[sage-devel] Re: screen output of compilation

2016-07-15 Thread Dima Pasechnik
On Friday, July 15, 2016 at 12:27:03 PM UTC+1, chris wuthrich wrote: > > Hi all. > > When I do make or sage -b each time there is now a huge print > > python_packages = ['sage', 'sage.lfunctions', > 'sage_setup.autogen.pari.doc'] > python_data_files = [('solverconf_helper.h'])] > > to

Re: [sage-devel] Re: spkgs assumed for doctesting but not default installed

2016-07-15 Thread Johan S . H . Rosenkilde
Hi, Sorry for not getting pack to this thread before. I'm still having this issue that newly compiled Sage is missing many packages. Overnight I did `make distclean && make --trace --debug=bvjm` on Sage 7.3.beta7 with #20926 applied (gcc6.1 C++ workarounds). I had downgraded my Make to version

[sage-devel] screen output of compilation

2016-07-15 Thread chris wuthrich
Hi all. When I do make or sage -b each time there is now a huge print python_packages = ['sage', 'sage.lfunctions', 'sage_setup.autogen.pari.doc'] python_data_files = [('solverconf_helper.h'])] to the screen. Is there a way to hide this? It annoys me that I have to scroll up to find

[sage-devel] #20611 needs review : more functionalities for mq.SBox

2016-07-15 Thread Rusydi H. Makarim
Hi, I committed a patch to provide more features for SAGE mq.SBox with two helpers to construct bigger S-Box from smaller S-Boxes (Feistel and MISTY construction). I would appreciate if someone willing to review the ticket. https://trac.sagemath.org/ticket/20611 Best Regards, -- Rusydi H.

[sage-devel] About certificate-options

2016-07-15 Thread Jori Mäntysalo
There was some discussion about how to write docstring for certificates, see for example https://trac.sagemath.org/ticket/20972 and https://trac.sagemath.org/ticket/20940 . And just now #20778 and #20689 adds certificate-options. Of course a minor thing, but should we try to unify this?