Hello,

an update on the python3 status. Moving slowly, long way ahead.

* currently, building sage with "SAGE_PYTHON3=yes" breaks much more early 
than previously. This prevents to monitor seriously the progress towards 
python3 and should be investigated as soon as possible.

* step 1A : cythonizing : there remains only a few calls to cmp() that 
prevents cythonization of our pyx files

-- some of them will maybe be handled by ticket #22549, that changes the 
semantics of equality for real and complex interval fields.

-- some other may require more work, as started in ticket #22029

* step 1B : compilation of the pyx files : here there are a few problems 
remainings including at least

-- need to adapt the weak dictionaries (ticket #22305)

-- a problem with InheritComparison metaclass (#22403)

* step 1C:  compilation of all standard packages. Some problematic ones are

-- sagenb (to be phased out soon ?)

-- conway database ?

* step 2A: make sure that python files compiles (not yet possible to try to 
do that, or just blindly)

-- the calls to cmp() in Python code are still very numerous.

-- it seems that zip has now been fully futurized

-- the same for range is underway

-- some other major issues will be unicode and integer division

* step 2B: doctests pass

-- this is only possible to consider as a task once everything else is 
solved, so this is not for soon

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.

Reply via email to