On Sun, Jan 5, 2020 at 10:06 PM Nils Bruin <nbr...@sfu.ca> wrote: > > I think our wiki vetoes that idea. See > https://wiki.sagemath.org/Python3-Switch : > > Compiling with Python 2 > > After version 9.0, if you really want so, you can still build and use > SageMath with Python 2, as follows. > > make configure > ./configure --with-python=2 > make build > > Beware that you will need to call the second line again if you ever call > "make distclean". > > This will work until version 9.1 at least. Then the backward compatibility > with Python 2 will no longer be ensured. > > If you want to drop py2 compatibility very soon, the only option is to > release 9.1 basically right now, identical to 9.0, and then get on with > developing 9.2. That's a nasty thing to do. Based on previous release > schedules, people would be justified in expecting that <=9.1 is the "current" > release until at least June 2020 or so. So we're stuck with py2 compatibility > until that time.
I agree with Nils. There should be at least a one release deprecation period. Also, while I don't think we use any kind of real semantic versioning, I think we should name a Python 3-only release 10.0 as it's a very major backwards-incompatibility change. Instead for 9.1 let us display a prominent deprecation message in any Python 2 builds when running Sage, including a link to a guide for porting existing code (for Sage there is not all that much to do--mostly any generic Python 2 to 3 porting guide will do, plus some Sage-specific caveats of which I can't think of many). -- 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/CAOTD34aWri4C-U4XqGHcO77UB6%2BNgAvvbofBtxfuWkgU4UGR4w%40mail.gmail.com.
