[sage-devel] Fwd: SageMath packaging status update

2016-08-09 Thread Jan Groenewald
Might of interest to some here. Please join the mailing list if you can help. -- Forwarded message -- From: Tobias Hansen Date: 10 August 2016 at 01:17 Subject: SageMath packaging status update To: "debian-scie...@lists.debian.org" Hi Debian Science, I thought I'd give you an

[sage-devel] fast_callable interpreter for MPC?

2016-08-09 Thread Nils Bruin
A quick inquiry: I noticed that fast_callable(...,domain=RealField(...) ) results in instances of RRInterpreter, which is nice and fast. On the other hand, fast_callable(...,domain=ComplexField(...)) results in a more generic type (and something that is considerably slower, at least for polynom

Re: [sage-devel] Re: Should warnings display a traceback?

2016-08-09 Thread Travis Scrimshaw
On Tuesday, August 9, 2016 at 2:31:16 AM UTC-5, Jeroen Demeyer wrote: > > On 2016-08-09 00:21, Travis Scrimshaw wrote: > > If we do this, then deprecation warnings would also get full tracebacks, > > which is something I think we should not have on by default. > > Why not? It's not that you ne

Re: [sage-devel] patchbot server refuses to connect

2016-08-09 Thread William Stein
OK, leaving it as -- not rebooting. On Tue, Aug 9, 2016 at 12:51 AM, Frédéric Chapoton wrote: > Please do not reboot. We are currently doing an rsync for the database, > and we decided to turn the server off for a moment. > > Thierry Monteil is doing the job. Maybe he can tell us about the stat

[sage-devel] Re: Issues when building Sage with --with-mp=gmp

2016-08-09 Thread leif
leif wrote: > Francois Bissey wrote: >> >>> On 31/07/2016, at 18:54, leif wrote: >>> >>> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0): >>> >>> -- >>> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.py

Re: [sage-devel] increasing verbose level for sub-routines

2016-08-09 Thread William Stein
On Tuesday, August 9, 2016, Volker Braun wrote: > The only good way is to rip out the "verbose" thing and replace it with > the Python logging module. Then its easy to have different loggers for your > code and for the flint interface, and make them log in different levels > and/or different outp

[sage-devel] Re: increasing verbose level for sub-routines

2016-08-09 Thread Volker Braun
The only good way is to rip out the "verbose" thing and replace it with the Python logging module. Then its easy to have different loggers for your code and for the flint interface, and make them log in different levels and/or different output streams. On Tuesday, August 9, 2016 at 11:42:32

[sage-devel] Re: Issues when building Sage with --with-mp=gmp

2016-08-09 Thread leif
Francois Bissey wrote: > >> On 31/07/2016, at 18:54, leif wrote: >> >> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0): >> >> -- >> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.pyx # >> Killed due t

[sage-devel] Re: Should warnings display a traceback?

2016-08-09 Thread leif
Jeroen Demeyer wrote: > On 2016-08-09 00:21, Travis Scrimshaw wrote: >> However, it >> might be good to have an option somewhere to enable is (and hopefully it >> won't get lost in the forest that is Sage). > > Well, it seems we both agree that there are too many options already. You cannot have

[sage-devel] d3js question.

2016-08-09 Thread Thierry Dumont
Hello, It seems that Sage can make some usage of d3.js -> http://sagemanifolds.obspm.fr/doc/reference/graphs/sage/graphs/graph_plot_js.html -> their exists a d3js package (which seems to install the library / javascript) But d3.js seems to be used only to draw graphs. Am I wrong ? >From an othe

Re: [sage-devel] fplll 5.0 in sage

2016-08-09 Thread Jean-Pierre Flori
Yes! Did you open a ticket for this? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to

[sage-devel] increasing verbose level for sub-routines

2016-08-09 Thread Daniel Krenn
Say I have some function doing something: sage: def f(M): : A = M # something will be done here : verbose('something', 1) : iA = A^(-1) : return iA Setting the level of verbosity to 1 gives the output sage: set_verbose(1) sage: f(Matrix([[1, 2], [3, 4]])) verbose

Re: [sage-devel] patchbot server refuses to connect

2016-08-09 Thread Frédéric Chapoton
Please do not reboot. We are currently doing an rsync for the database, and we decided to turn the server off for a moment. Thierry Monteil is doing the job. Maybe he can tell us about the status ? Le mardi 9 août 2016 08:18:25 UTC+2, William a écrit : > > On Mon, Aug 8, 2016 at 10:11 PM, Ralf

Re: [sage-devel] Re: Should warnings display a traceback?

2016-08-09 Thread Jeroen Demeyer
On 2016-08-09 00:21, Travis Scrimshaw wrote: If we do this, then deprecation warnings would also get full tracebacks, which is something I think we should not have on by default. Why not? It's not that you need to put the complete traceback in the doctest, you can use ... for that. So you woul