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

[Frédéric Chapoton]

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 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 needed fixing. 
>
> > 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 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 post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[E. Madison Bray]

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 needed fixing.

> 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 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Frédéric Chapoton]

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 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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Frédéric Chapoton]

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 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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Frédéric Chapoton]

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 remains many hard-to-fix issues. Please help if you can.

* Matroid, dynamics and combinat people should care for their code. The 
cluster code needs particular work.

* We should also strive to make all tests pass in rings/

* An expert is required on src/sage/misc/classcall_metaclass.pyx

Frédéric



-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status report

[Frédéric Chapoton]

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 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 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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status report

[Jeroen Demeyer]

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 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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] python3 status report

[Frédéric Chapoton]

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 doctests. Among those, 74 
files have 1 failing doctest.

(2) the most badly failing file is "explain_pickle" with 70 failing 
doctests. Hopefully, this will be treated very carefully by Erik M. Bray

(3) after that, we still have problems with graph, where generic_graph.py 
has 50 failing doctests. But good progress was made by David Coudert,

(4) then, various small issues, such as sorting sets and dictionaries, etc. 
Some good python3 changes are blocked by the long awaited ticket 
https://trac.sagemath.org/ticket/23572

*STATEMENT *: I would to advocate that **every developer switch to python3 
NOW**.

This will help to prevent regressions, as the one that happened recently in 
elliptic curves. This will also motivate people to fix the part of the code 
base that they use and that still fails.

Please vote !

Frédéric

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] python3 status report

[Frédéric Chapoton]

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 doctests. Among these files, *only 3 files have more than 100 
failing doctests*, and 122 files have exactly one failing doctest.

It is not easy to describe the remaining problems. There are lots of small 
issues, and at least one large issue about sorting vertices in graphs, 
where some work is being done right now. Another issue is related to 
something that would change all bases in the spaces of modular symbols, 
therefore changing many doctests that have hardcoded the choice of basis. 
This is ticket https://trac.sagemath.org/ticket/25301 for those interested 
in this matter.

One concern now is to start trying to prevent any regression to happen 
(because this is already happening). Should we require people to check that 
they do not introduce more failing doctests with python3 than the existing 
ones ? Could somebody provide a buildbot so that at least the python3 build 
is checked ?

The documentation still does not build, currently because of a regression 
in the manifolds folder, but mainly because of some problems with sphinx, 
that apparently is not seeing some of the classes. 
See https://trac.sagemath.org/ticket/26449 
and https://trac.sagemath.org/ticket/26522

Sage is now working quite well with python3, even if not perfectly. But 
more work (not so easy) is needed to finish the task. Help is welcome.

Frédéric

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] python3 status

[Frédéric Chapoton]

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 (sigh).

There has been recent progress on the pexpect interfaces and lib 
interfaces, so this sage3 is now somewhat usable. Try it !

Our next goal is to get the documentation build. After that, one will have 
to make all doctest pass, but we are still a *long* way from that.
Another interesting step would be to be able to launch the jupyter notebook 
with sage3. Currently, it looks for the sage kernel in the python2 library 
(no ticket yet).

The current result of trying to build the doc can be seen here : 

https://patchbot.sagemath.org/log/0/Ubuntu/18.04/x86_64/4.15.0-20-generic/petitbonum/2018-05-27%2021:55:21?plugin=docbuild

Apparently, we are not so far to manage building the documentation. Two 
important issues, responsible for many errors in docbuilding:

(A) fix some heavy problem of hash in the manifolds code, 
see https://trac.sagemath.org/ticket/25393

(B) need to reactivate the build of sagenb in python3 : 
see https://trac.sagemath.org/ticket/22431

Ticket 22431 above need people to check (1) that the upgraded sagenb works 
smoothly on python2 and (2) that sage3 still builds and starts after 
building sagenb.

(note that even after 22341, sagenb will not work in sage3, due to some 
missing parts of twisted, that require upgrading twisted.)

Does somebody care ?

Frédéric

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Erik Bray]

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: 2017-10-03   │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> sage: 3*3
> 9
> sage: parent(_)
> Integer Ring
>
>
> Cool, no ? Or maybe nobody cares ?
>
> 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 problem.

Very cool. I still hope to help out more with this, especially the
string problems which I'm practiced at dealing with.  I was starting
to several weeks ago when I tried to reproduce the Python 3 issues
from scratch, but then got side-tracked, and then went on a long trip,
so now I'll need to start over again on a Python 3 build.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Jeroen Demeyer]

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 with both Python 2 and Python 3. This means that some Python 
2 only code like xrange() or dict.iteritems() works in Cython with 
Python 3. Also, some Python 3 only code works on Python 2. For example, 
keyword-only arguments, f-strings, new super(), yield from.


--
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Volker Braun]

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+2, 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? 
>
> 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 testing that now, 
> to see where the issues will lie? 
>
> John 
>
> On 13 October 2017 at 20:19, 'Julien Puydt' via sage-devel 
>  wrote: 
> > 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 problem. 
> > 
> > Why are unicode and hash problems? 
> > 
> > Snark on #sagemath 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Kwankyu Lee]

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 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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Frédéric Chapoton]

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 "2to3" ; another one is "pep8" (to find 
deprecated syntax, for example syntax of raise).
Another way is to try to launch your module using "python -3".

The best way forward is to move as quickly as possible to a working 
python3+sage. We still have for example to make sage doctest system work 
with python3.

Frederic

https://stackoverflow.com/questions/40886456/how-to-detect-if-code-is-python-3-compatible
https://stackoverflow.com/questions/40815079/checking-code-for-compatibility-with-python-2-and-3



Le samedi 14 octobre 2017 11:51:01 UTC+2, John Cremona a écrit :
>
> 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 testing that now, 
> to see where the issues will lie? 
>
> John 
>
> On 13 October 2017 at 20:19, 'Julien Puydt' via sage-devel 
>  wrote: 
> > 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 problem. 
> > 
> > Why are unicode and hash problems? 
> > 
> > Snark on #sagemath 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[John Cremona]

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 testing that now,
to see where the issues will lie?

John

On 13 October 2017 at 20:19, 'Julien Puydt' via sage-devel
 wrote:
> 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 problem.
>
> Why are unicode and hash problems?
>
> Snark on #sagemath
>
> --
> 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

['Julien Puydt' via sage-devel]

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 problem.

Why are unicode and hash problems?

Snark on #sagemath

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] python3 status

[Jori Mäntysalo]

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

[Frédéric Chapoton]

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 notebook interface.│
│ Type "help()" for help.│
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
sage: 3*3
9
sage: parent(_)
Integer Ring


Cool, no ? Or maybe nobody cares ?

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 problem.

Frederic

-- 
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.