[sage-devel] The opportunity of Python 3 migration

2019-09-01 Thread Thierry
Hi, it seems to me that Python 3 migration should not only be a syntax adaptation (like print('blah')), unicode, or the mitigation of issues related to the fact that different objects are not always comparable. It should also take into account some deep changes in the logic. Lists vs Iterables

Re: [sage-devel] The opportunity of Python 3 migration

2019-09-01 Thread Luca De Feo
+1 to this! On Sun, Sep 1, 2019 at 9:14 PM Thierry wrote: > > Hi, > > it seems to me that Python 3 migration should not only be a syntax > adaptation (like print('blah')), unicode, or the mitigation of issues > related to the fact that different objects are not always comparable. > > It should al

[sage-devel] Re: The opportunity of Python 3 migration

2019-09-01 Thread mmarco
I think the change you propose is reasonable. However, it sounds like a lot of work, and the support for python2 ends in just a few months. We should aim to release a python3 based release that passes all tests before the end of the year. Do you think it is reasonable to do these deep changes i

[sage-devel] Re: The opportunity of Python 3 migration

2019-09-01 Thread Nils Bruin
On Sunday, September 1, 2019 at 12:14:51 PM UTC-7, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > it seems to me that Python 3 migration should not only be a syntax > adaptation (like print('blah')), unicode, or the mitigation of issues > related to the fact that different objects are not al

Re: [sage-devel] Re: The opportunity of Python 3 migration

2019-09-01 Thread Luca De Feo
I think the List vs Iterables item is totally doable on time. The rest is maybe more complicated, but even if it's only 50% done it's ok. Luca On Sun, Sep 1, 2019 at 11:50 PM Nils Bruin wrote: > > On Sunday, September 1, 2019 at 12:14:51 PM UTC-7, Thierry > (sage-googlesucks@xxx) wrote: >> >> H

[sage-devel] Unpickling problem (backwards incompatibility) in Python 3

2019-09-01 Thread Simon King
Hi! I have a pickle that I can unpickle in Sage-with-Python-2, but it fails to unpickle in Sage-with-Python-3, because of some UnicodeError. Strangely, when I read the pickle as a string open('path/to/file.sobj').read() then it fails with a (different?) UnicodeError in Python-3. The details (n

[sage-devel] Re: The opportunity of Python 3 migration

2019-09-01 Thread David Coudert
> A few examples: vertices() and edges() of graphs should not be lists, > but keep links to the graph itself. For edges, see https://trac.sagemath.org/ticket/27408 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gr