Re: [sage-devel] python3 status report (mi-april of last python2 year)

No idea why, but there are many doctests failures in these files. I have just created https://trac.sagemath.org/ticket/27692 and https://trac.sagemath.org/ticket/2769 3 Le mercredi 17 avril 2019 18:15:15 UTC+2, E. Madison Bray a écrit : > > On Wed, Apr

Re: [sage-devel] python3 status report (mi-april of last python2 year)

On Wed, Apr 17, 2019 at 4:52 PM Frédéric Chapoton wrote: > > and also the file src/sage/misc/nested_class.pyx needs another expert (or the > same) Could you explain why, or make a ticket? IIRC I fixed stuff in both those modules a long time ago and that it was mostly just trivial stuff that nee

Re: [sage-devel] python3 status report (mi-april of last python2 year)

and also the file src/sage/misc/nested_class.pyx needs another expert (or the same) Frederic Le lundi 15 avril 2019 14:28:41 UTC+2, Jeroen Demeyer a écrit : > > On 2019-04-15 13:56, Frédéric Chapoton wrote: > > * An expert is required on src/sage/misc/classcall_metaclass.pyx > > Is there a tic

Re: [sage-devel] python3 status report (mi-april of last python2 year)

No. Feel free to open one. Le lundi 15 avril 2019 14:28:41 UTC+2, Jeroen Demeyer a écrit : > > On 2019-04-15 13:56, Frédéric Chapoton wrote: > > * An expert is required on src/sage/misc/classcall_metaclass.pyx > > Is there a ticket for that? > -- You received this message because you are subs

Re: [sage-devel] python3 status report (mi-april of last python2 year)

On 2019-04-15 13:56, Frédéric Chapoton wrote: * An expert is required on src/sage/misc/classcall_metaclass.pyx Is there a ticket for that? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] python3 status report (mi-april of last python2 year)

Hello, sage-with-python3 (now using python 3.7.3) has now *less than 100 files* (94 precisely) with failing doctests, for a total of *324 failing doctests*. Among these, 34 files have a single failing doctest. A detailed summary can be found here : https://trac.sagemath.org/ticket/26212 There

Re: [sage-devel] python3 status report

It is blocking https://trac.sagemath.org/ticket/26792 Le dimanche 27 janvier 2019 15:56:02 UTC+1, Jeroen Demeyer a écrit : > > On 2019-01-27 14:23, Frédéric Chapoton wrote: > > Some good python3 changes are blocked by the long awaited ticket > > https://trac.sagemath.org/ticket/23572 > > What

Re: [sage-devel] python3 status report

On 2019-01-27 14:23, Frédéric Chapoton wrote: Some good python3 changes are blocked by the long awaited ticket https://trac.sagemath.org/ticket/23572 What do you mean with that? It's a ticket adding doctests for a book, how is that related to Python 3 porting? -- You received this message be

[sage-devel] python3 status report

Hello everybody, here is a small progress report on porting sage to python3. Good, but still too slow for my taste. The sooner we can catch up with jupyter, the better.. (1) with the latest beta (8.7.b1), there are now exactly 200 files having failing doctests, and a total of 866 failing doctes

[sage-devel] python3 status report

Dear all, Here is a short report on the current progress towards *making* *sage compatible with python3*. The last few releases have seen a good progress, monitored in https://trac.sagemath.org/ticket/26212 There remains now 414 files having failing doctests for a total of 3206 failing doctes

[sage-devel] python3 status

Hello, here is a small report on the *slow* progress towards python3-compatibility for sage. Sage is already building and starting with python3 since some time already. It is explained in https://trac.sagemath.org/ticket/15530 how to get a python3-sage. One can note an even longer startup time

Re: [sage-devel] python3 status

On Fri, Oct 13, 2017 at 5:56 PM, Frédéric Chapoton wrote: > Hello, > > I have reached this point with the ugly python3 experimental branch > "public/python3-experiment-8.1.b7": > > > ┌┐ > │ SageMath version 8.1.beta7, Release Date

Re: [sage-devel] python3 status

On 2017-10-14 11:50, John Cremona wrote: How can we be sure that new code witten by people (like me) who are not python2/3 experts does not regress? I think it's also important to mention that Cython is quite different from plain Python in this regard. Cython generally tries to be compatible

Re: [sage-devel] python3 status

There are a few guards in place * Doctests don't accept print statements any more * There is a unit test that checks that code is syntactically Py3 Thats not enough to catch .iteritems, for example, but we'll get better test coverage over time. On Saturday, October 14, 2017 at 11:51:01 AM UTC

Re: [sage-devel] python3 status

On Saturday, October 14, 2017 at 6:51:01 PM UTC+9, John Cremona wrote: > > How can we be sure that new code witten by people (like me) who are > not python2/3 experts does not regress? This would help. While coding on Sage, I refer to Python 3 reference manual :-) -- You received this messa

Re: [sage-devel] python3 status

There is no simple and perfect way to really test that fully now. Some things that can be done right now in the code of packages : * check that print is used in a python3 compatible way * check that cmp() is not used * check that .iteritems, .iterkeys are not used An useful diagnostic tool is "2

Re: [sage-devel] python3 status

How can we be sure that new code witten by people (like me) who are not python2/3 experts does not regress? Also, I can see that projects which build on top of Sage will one day have to make sure that their code is all python3-compliant (I am thinking of the LMFDB). What's the simplest way of tes

Re: [sage-devel] python3 status

Hi, Le 13/10/2017 à 17:56, Frédéric Chapoton a écrit : > Cool, no ? Or maybe nobody cares ? Extremely cool! > Many things are still not working. The cmp problem has been much > reduced, but still not fully fixed. On our way is a large-scale unicode > problem, and maybe another large scale hash p

Re: [sage-devel] python3 status

On Fri, 13 Oct 2017, Frédéric Chapoton wrote: Cool, no ? Or maybe nobody cares ? Cool, yes! -- Jori Mäntysalo

[sage-devel] python3 status

Hello, I have reached this point with the ugly python3 experimental branch "public/python3-experiment-8.1.b7": ┌┐ │ SageMath version 8.1.beta7, Release Date: 2017-10-03 │ │ Type "notebook()" for the browser-based