On Fri, Jan 10, 2020 at 1:03 AM Volker Braun <vbraun.n...@gmail.com> wrote: > > * I think its not too difficult to write code that is Python 2.7 + 3.x (for > high enough x) compatible, so its not a super pressing issue > * We do have a Python 2 buildbot to test for regressions > * For semver reasons we should drop Python 2.7 support in Sage 10, not 9.1 > > Having said that, I'm fine with an accelerated Sage 9 -> Sage 10 schedule, > maybe a month or two instead of the usual 3-4. Though first we should take > the opportunity and see if there are any outstanding Python 3 bugs now that > we have more data. For example it would be nice if a build with > SAGE_DEBUG=yes would pass tests. There are a few more regressions, e.g. #28817
Accelerated is fine, but I should add that fully *removing* Python 2 support is not a trivial task either (it's mostly mechanical work, but there's a LOT of it). https://trac.sagemath.org/ticket/28000 has a few steps towards it but is far from complete. Fully removing Python 2-isms from the codebase is not necessarily a prerequisite to dropping Python 2 support, but I would be hesitant to leave a monstrous partially-hybrid codebase around for too long. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34Z%3DpXaDP5ByS2pAf45HgL-0gOkrTdcGFzSZsAc24rgR%3Dw%40mail.gmail.com.
