[sage-devel] Re: screen output of compilation

2016-07-16 Thread leif
Travis Scrimshaw wrote: > > I added that in #20712 > > If you think its annoying then revert it, fine with me. > > > It is somewhat of a mild annoyance to me, but I think it would be good > to either redirect the output to a log file or have another option to > display it. +1 I

[sage-devel] Re: screen output of compilation

2016-07-16 Thread Travis Scrimshaw
> I added that in #20712 > > If you think its annoying then revert it, fine with me. > It is somewhat of a mild annoyance to me, but I think it would be good to either redirect the output to a log file or have another option to display it. Best, Travis -- You received this message because

[sage-devel] Re: screen output of compilation

2016-07-16 Thread chris wuthrich
I added that in #20712 > Thanks, now I know where to disable it. I am fine just doing it just for me. I am sure you had good reasons to introduce it. I will leave it to others annoyed by it (if any) to revert it or to redirect it to a file rather than the screen. Chris -- You received this

[sage-devel] Re: screen output of compilation

2016-07-16 Thread Volker Braun
I added that in #20712 If you think its annoying then revert it, fine with me. On Friday, July 15, 2016 at 1:27:03 PM UTC+2, 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-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