Re: [sage-devel] Switch to Python 3 by default

2019-10-27 Thread kcrisman
> > > > BUT be damn sure to document the way to compile for/with Python 2 in all > places we currently doncument how to compile for Python 3. >> >> >> +1 Will py2 buildbots or regular testers still exist? -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Problems launching jupyter browser window and threejs browser window

2019-10-27 Thread Eric Gourgoulhon
Le dimanche 27 octobre 2019 15:36:45 UTC+1, jplab a écrit : > > Hi everyone, > > I wanted to test the following ticket on sage 9.0beta2: > > https://trac.sagemath.org/ticket/28658 > > So I wrote the following in the terminal: > > sage: p = polytopes.icosahedron() > sage: p.plot() > Launched html

Re: [sage-devel] Problems launching jupyter browser window and threejs browser window

2019-10-27 Thread Dima Pasechnik
On Sun, Oct 27, 2019 at 4:36 PM jplab wrote: > > Hi everyone, > > I wanted to test the following ticket on sage 9.0beta2: > > https://trac.sagemath.org/ticket/28658 > > So I wrote the following in the terminal: > > sage: p = polytopes.icosahedron() > sage: p.plot() > Launched html viewer for

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

2019-10-27 Thread Simon King
Hi Vincent, On 2019-10-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > This was an easy one. The following shows that SR is just > broken pi is rational! > > sage: q = continued_fraction(pi).convergent(100) > sage: q >

Re: [sage-devel] Re: Switch to Python 3 by default

2019-10-27 Thread Emmanuel Charpentier
+1 for Dima's remark. Has anybody used the old Sage notebook with a Python 3-based Sage ? Le dimanche 27 octobre 2019 16:52:34 UTC+1, Dima Pasechnik a écrit : > > +1, although it seems that #25837 (making sagenb optional) should happen > first. > > On Sun, Oct 27, 2019 at 4:52 PM mmarco > >

Re: [sage-devel] Switch to Python 3 by default

2019-10-27 Thread Emmanuel Charpentier
In linked ticket : Because 3 x 3 = 9 and we are at 9.0.beta3 these are three reasons to do the switch Do you plan to start a sage_numerology package ??? ;-) Heavens... And, while you are at it, why not a sage-astrology or a a sage_econometrics package ? ;-]... Shuddering... That said, +1

Re: [sage-devel] Re: Switch to Python 3 by default

2019-10-27 Thread Dima Pasechnik
+1, although it seems that #25837 (making sagenb optional) should happen first. On Sun, Oct 27, 2019 at 4:52 PM mmarco wrote: > > If all the issues ar solved... sure. I was even surprised that we started > haviong betas of version 9 with python 2 (I assumed that the witch to version > 9 would

[sage-devel] Re: Switch to Python 3 by default

2019-10-27 Thread mmarco
If all the issues ar solved... sure. I was even surprised that we started haviong betas of version 9 with python 2 (I assumed that the witch to version 9 would be mostly about the transition to python 3). +1 El domingo, 27 de octubre de 2019, 1:58:23 (UTC+2), Volker Braun escribió: > > Maybe I

[sage-devel] Problems launching jupyter browser window and threejs browser window

2019-10-27 Thread jplab
Hi everyone, I wanted to test the following ticket on sage 9.0beta2: https://trac.sagemath.org/ticket/28658 So I wrote the following in the terminal: sage: p = polytopes.icosahedron() sage: p.plot() Launched html viewer for Graphics3d Object Then, a Firefox browser window opens with Firefox's

[sage-devel] Re: Need help testing #27122 and #27103

2019-10-27 Thread jplab
Which platforms need testing precisely? and which platforms were tested? J-P Le vendredi 25 octobre 2019 22:28:03 UTC+2, Jonathan Kliem a écrit : > > Hi, I would appreciate some help testing #27122 > and possibly on top of that > #27103

[sage-devel] Re: Switch to Python 3 by default

2019-10-27 Thread jplab
+1 Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit : > > Maybe I missed it, but I didn't find a ticket for that. I think now would > be a good time to flip the switch, though. Any thoughts? > -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Manifolds: Using Multiprocessing with Functions causes Error

2019-10-27 Thread Eric Gourgoulhon
This is unfortunately a known bug: parallelism does not work with symbolic functions. The ticket devoted to this issue is https://trac.sagemath.org/ticket/27492 Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

[sage-devel] Re: Switch to Python 3 by default

2019-10-27 Thread Eric Gourgoulhon
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit : > > Maybe I missed it, but I didn't find a ticket for that. I think now would > be a good time to flip the switch, though. Any thoughts? > +1 Eric. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Switch to Python 3 by default

2019-10-27 Thread VulK
+1 * Samuel Lelievre [2019-10-26 22:29:40]: +1 -- 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 view this

[sage-devel] Manifolds: Using Multiprocessing with Functions causes Error

2019-10-27 Thread Michael Jung
sage: Parallelism().set(nproc=4) sage: M = Manifold(2, name='S2', latex_name=r'S^2', start_index=1) sage: U = M.open_subset('U') ; V = M.open_subset('V') sage: M.declare_union(U,V) # M is the union of U and V sage: c_xy. = U.chart() ; c_uv. = V.chart() sage: xy_to_uv = c_xy.transition_map(c_uv,