On 2016-08-14 14:41, Frédéric Chapoton wrote:
Otherwise, one will have to get rid /by hand/ of all the `__cmp__`
methods everywhere, that will become obsolete in python3.

Don't confuse the cmp() function with __cmp__() methods! Getting rid of cmp() and getting rid of __cmp__() are a priori different issues.

An easy but ugly solution for both would be to simply keep supporting cmp() and __cmp__() in Python 3.

For cmp(), we could try to "port" it to Python 3. We could write a cmp() function which behaves just like the cmp() from Python 2.

For __cmp__(), we could support it at least in the coercion model (i.e. anything inheriting from Element).

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