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

[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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8ee25ea9-ef54-4540-bb56-7da5a1e0ce7e%40googlegroups.com.

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

[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 viewer for Graphics3d Object
>
> Then, a Firefox browser window opens with Firefox's "pingponging ball of 
> Death" of an eternally loading window...
>
>

Works for me (on the same ticket branch). This is with Ubuntu 18.04 + 
Firefox 70.0. What is your system? 


> While we are here, on another train of thoughts: is it me or viewing 
> polyhedron with threejs does not show the edges?
>

Same issue here.
Note that 

sage: icosahedron()

shows the edges.

Eric.
 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7435fb68-95d6-4ef9-b100-ef2cfbef097a%40googlegroups.com.

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

[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 Graphics3d Object
>
> Then, a Firefox browser window opens with Firefox's "pingponging ball of 
> Death" of an eternally loading window...
>
> The same thing occurs with
>
> sage -notebook
>
> Previously, I've been having problems with launching jupyter, but copy-pasting
> the link given in the terminal in the address bar always worked, so I had my 
> workaround.
> But I have grown tired of this workaround and I thought maybe someone knew 
> how to solve this?
>
> I've just done a "make distclean" for another reason, have a freshly compiled 
> sage and moved ".sage" to ".sage_old" to see if
> this changes anything: Nope.
>
> I am running debian buster with firefox being my default browser.
>
> Any ideas would be appreciated!
>
> While we are here, on another train of thoughts: is it me or viewing 
> polyhedron with threejs does not show the edges?

I too don't see the edges of the icosahedron while viewin the in
jupyter notebook.
Could you open a ticket for this?

>
> J-P
>
> --
> 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 discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/8dac1a83-f36d-4a7d-8769-53b4c0e5d73b%40googlegroups.com.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3okwX-UOLyb4tocbghq113zSBYHpeXSGZ-wNAMbKcexg%40mail.gmail.com.

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

[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
> 8736149038303113005348154524599771853409352442745266/2780802606066896232581239559281727773240004199722661
> sage: bool(pi == q)
> True

Nice!

Best regards,
Simon

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/qp4jg7%24mui%241%40blaine.gmane.org.

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

[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 > 
> 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 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 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" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/76975173-bd00-44ed-af88-8d388f061f3a%40googlegroups.com.
>  
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8df2fc8c-5a3d-4d29-bd09-3d8d3fa70422%40googlegroups.com.

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

[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 for switching to Python3 by default.

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.

Le dimanche 27 octobre 2019 02:27:51 UTC+2, vdelecroix a écrit :
>
>
> https://trac.sagemath.org/ticket/28660 
>
>
> Le 26/10/2019 à 17:20, François Bissey a écrit : 
> > +1 
> > 
> >> On 27/10/2019, at 12:58 PM, Vincent Delecroix <20100.d...@gmail.com 
> > wrote: 
> >> 
> >> +1 
> >> 
> >> Le 26/10/2019 à 16:58, 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" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-...@googlegroups.com . 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/4a982d46-747e-abaf-a76a-c7f5764c363f%40gmail.com.
>  
>
> > 
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d264dae8-9a7e-4e6b-aa49-c4d7ce1a7fa3%40googlegroups.com.

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

[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 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 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" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/76975173-bd00-44ed-af88-8d388f061f3a%40googlegroups.com.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3LLCiLC_3oAc9_44Nii6hgrpT6EB3uqRDz4Vj7_aHOUw%40mail.gmail.com.

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

[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 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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/76975173-bd00-44ed-af88-8d388f061f3a%40googlegroups.com.

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

[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 "pingponging ball of 
Death" of an eternally loading window...

The same thing occurs with

sage -notebook

Previously, I've been having problems with launching jupyter, but 
copy-pasting 
the link given in the terminal in the address bar always worked, so I had 
my workaround.
But I have grown tired of this workaround and I thought maybe someone knew 
how to solve this?

I've just done a "make distclean" for another reason, have a freshly 
compiled sage and moved ".sage" to ".sage_old" to see if 
this changes anything: Nope.

I am running debian buster with firefox being my default browser.

Any ideas would be appreciated!

While we are here, on another train of thoughts: is it me or viewing 
polyhedron with threejs does not show the edges?

J-P

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8dac1a83-f36d-4a7d-8769-53b4c0e5d73b%40googlegroups.com.

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

[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 .
>
> Both tickets have instructions for testing in their description, which are 
> hopefully helpful. The first ticket adds a compile argument to optimize 
> sage for the current machine (unless SAGE_FAT_BINARIES is set).
> Naturally, the behavior depends very much on the machine and we need a 
> variety of tests, to see if it is ok. The compile argument `-march=native` 
> is supposed to change things only for the better, but who knows what will 
> or can happen.
>
> The second ticket makes use of the first and is also very much platform 
> dependent.
>
> Thank you,
>
> Jonathan
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d03b0a77-8119-4c8c-86a4-aa884889dbd8%40googlegroups.com.

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

[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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9edb6730-3e4a-4dc8-9262-16e4bb7a23b6%40googlegroups.com.

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

[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 from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/10c20a50-391c-41e6-9a02-391a54f7e0fa%40googlegroups.com.

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

[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 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f59bb2b9-03d4-4c86-84a2-c6eeabd861a7%40googlegroups.com.

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

[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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ca69beab-7948-4c5a-8530-9bd13bd299d5%40googlegroups.com.


--
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20191027102802.GC9511%40bunion.

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

[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,
:   (x/(x^2+y^2), y/(x^2+y^2)),
:   intersection_name='W',
:   restrictions1= x^2+y^2!=0,
:   restrictions2= u^2+v^2!=0)
sage: uv_to_xy = xy_to_uv.inverse()
sage: eU = c_xy.frame() ; eV = c_uv.frame()
sage: a = function('a')
sage: g = M.metric('g')
sage: g[eU,1,1], g[eU,2,2] = a(x,y), a(x,y)
sage: g[eV,1,1], g[eV,2,2] = a(u,v), a(u,v)
sage: nab = g.connection('nab')

---RemoteTraceback
   Traceback (most recent call last)RemoteTraceback: 
"""
Traceback (most recent call last):
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/interface.py",
 line 708, in __init__
self._name = parent._create(value, name=name)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/maxima_lib.py",
 line 606, in _create
self.set(name, value)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/maxima_lib.py",
 line 515, in set
self.eval(cmd)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/maxima_lib.py",
 line 461, in _eval_line
maxima_eval("#$%s$" % statement)
  File "sage/libs/ecl.pyx", line 804, in sage.libs.ecl.EclObject.__call__ 
(build/cythonized/sage/libs/ecl.c:7779)
lispargs = EclObject(list(args))
  File "sage/libs/ecl.pyx", line 669, in sage.libs.ecl.EclObject.__init__ 
(build/cythonized/sage/libs/ecl.c:7313)
self.set_obj(python_to_ecl(args[0]))
  File "sage/libs/ecl.pyx", line 484, in sage.libs.ecl.python_to_ecl 
(build/cythonized/sage/libs/ecl.c:6357)
L=cl_cons(python_to_ecl(pyobj[0]),Cnil)
  File "sage/libs/ecl.pyx", line 465, in sage.libs.ecl.python_to_ecl 
(build/cythonized/sage/libs/ecl.c:6051)
return ecl_safe_read_string(s)
  File "sage/libs/ecl.pyx", line 385, in sage.libs.ecl.ecl_safe_read_string 
(build/cythonized/sage/libs/ecl.c:5530)
o = ecl_safe_funcall(read_from_string_clobj,o)
  File "sage/libs/ecl.pyx", line 364, in sage.libs.ecl.ecl_safe_funcall 
(build/cythonized/sage/libs/ecl.c:5297)
raise RuntimeError("ECL says: {}".format(
RuntimeError: ECL says: THROW: The catch MACSYMA-QUIT is undefined.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/multiprocessing/pool.py", 
line 121, in worker
result = (True, func(*args, **kwds))
  File "sage/misc/fpickle.pyx", line 105, in 
sage.misc.fpickle.call_pickled_function 
(build/cythonized/sage/misc/fpickle.c:2340)
res = eval("f(*args, **kwds)",sage.all.__dict__, {'args':args, 'kwds':kwds, 
'f':f})
  File "", line 1, in 
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/manifolds/differentiable/levi_civita_connection.py",
 line 518, in make_Connect
if ginv[i,s, chart]!=0:
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/manifolds/chart_func.py",
 line 1098, in __ne__
return not (self == other)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/manifolds/chart_func.py",
 line 1070, in __eq__
return bool(self.expr(self._calc_method._current) == other)
  File "sage/symbolic/expression.pyx", line 2919, in 
sage.symbolic.expression.Expression.__nonzero__ 
(build/cythonized/sage/symbolic/expression.cpp:19640)
return test_relation_maxima(self)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/symbolic/relation.py",
 line 492, in test_relation_maxima
m = relation._maxima_()
  File "sage/symbolic/expression.pyx", line 814, in 
sage.symbolic.expression.Expression._maxima_ 
(build/cythonized/sage/symbolic/expression.cpp:7814)
return super(Expression, self)._interface_(maxima)
  File "sage/structure/sage_object.pyx", line 675, in 
sage.structure.sage_object.SageObject._interface_ 
(build/cythonized/sage/structure/sage_object.c:5540)
X = I(s)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/interface.py",
 line 288, in __call__
return cls(self, x, name=name)
  File 
"/home/michi/GitProjects/sage/local/lib/python3.7/site-packages/sage/interfaces/interface.py",
 line 710, in __init__
raise TypeError(x)
TypeError: ECL says: THROW: The catch MACSYMA-QUIT is undefined.
"""

The above exception was the direct cause of the following exception:
TypeError Traceback (most recent call 
last) in ()> 1 nab = 
g.connection('nab')
/home/michi/GitProjects/sage/lo