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 <sage-devel@googlegroups.com> 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.
