There is no summary page for the cmp situation anywhere. You can look at #16537 and #17175
To know how this was solved in some cases, look at the tickets here: https://trac.sagemath.org/query?component=python3 having cmp in the title. Almost every case is different, because it can be either pyx_file/py_file, cython_class/python_class, coercion/no_coercion, and so on. To get rid of the call to cmp(), one often has to replace __cmp__ or _cmp_ by something else, and the something depends very much on the context. But maybe I am just saying nonsense. Jeoren, please correct me. Frederic Le jeudi 19 janvier 2017 08:58:24 UTC+1, Snark a écrit : > > Hi, > > On 19/01/2017 08:47, Frédéric Chapoton wrote: > > > The problem with cmp is quite hard, and it seems that every instance of > > cmp() must be handled separately. I have gained some experience on the > > subject, but given the lack of reviewers, this implies a very slow pace. > > This cmp problem should be the last remaining thing to handle before > > reaching 1A) and maybe even 1B) > > is there some place with a good summary of the cmp situation, and can > you point at some patches showing how the matter is fixed? > > Thanks, > > Snark on #debian-science > -- 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.
