VulK wrote: > Getting rid of __cmp__ would be the cleaner way but a simple grep on > $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are > definitions. Is there any way we can automate the process? > S.
I have to admit I fail to see the problem (perhaps Frédéric could elaborate a bit more). Deprecate cmp() and all __cmp__ methods (probably step by step), and temporarily (re)implement cmp() in Python3. Am I missing something? Deprecating the methods could certainly be automated, but I doubt it's worth the effort (at least to /fully/ automate that). -leif > * Frédéric Chapoton <fchapot...@gmail.com> [2016-08-14 05:41:01]: > >> As an intermediate step in our long way to python3, I would like to be >> able to compile all the .pyx files in py3. >> Except for #21246 (please review), the big remaining problem preventing >> to reach this goal is the removal of the builtin "cmp" in py3. >> One solution would be to have our own "cmp" that would boil down to py2 >> cmp in py2 and to something (but what ?) in py3. >> Otherwise, one will have to get rid by hand of all the `__cmp__` >> methods everywhere, that will become obsolete in python3. >> Please step in and talk out loud if you have a good strategy for this >> problem. -- 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.
