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
Since this thread had gone on quite long and it has perhaps gotten lost, I would just like to once again endorse Volker's suggestion here. We have already put enormous effort (hundreds of hours) into making Sage Python 2/3 compatible and making it relatively easy to write compatible code (and most new code will not even encounter these compatibility issues). Let us have a short release cycle for 9.1 and add a prominent deprecation message in 9.1 for Python 2 builds, then Sage 10.0 can implicitly start dropping support for Python 2. If there are some patches that are needed (e.g. to support ipython7) they will have to be applied eventually anyways so if some niche packing system must apply it for Sage 9.1 I see little harm. -- 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/CAOTD34bmEgw_CxV6qzwUi6tVa%3DhpeGO0BV4wUOULRUv4iNamVA%40mail.gmail.com.
