Am Freitag, 17. Januar 2020 16:07:08 UTC+1 schrieb E. Madison Bray: > > On Wed, Jan 15, 2020 at 2:37 AM Matthias Koeppe > <matthia...@gmail.com <javascript:>> wrote: > > > > On Tuesday, January 14, 2020 at 12:01:42 PM UTC-5, Frédéric Chapoton > wrote: > >> > >> So here is my proposal. > >> > >> * Starting from now, we allow ourselves to move on, using 9.1 betas and > further releases for external python3 updates, including switch to > ipython7, which seems to me the most urgent matter. But we also do not > introduce python3-only code in our own code base if we can avoid it. > > I'm not exactly sure what you mean by this, but it might be agreeable > to me: I'm completely okay with adding Python 3 only dependencies and > even *code/features* so long as it's done without breaking > backwards-compatibility. When it comes to sage-the-distribution > (which I sense is where most of this friction is coming from, and yet > another reason to better separate sage from the > sage-the-distribution), if there are dependencies you want to update > that are Python 3-only I'd say go for it, but make it a separate SPKG > so that previous versions of the dependency can still work on Python 2 > builds. >
As others have said already, supporting both python2 and python3 dependencies is much more work than only supporting python2 or only supporting python3 versions. I think dropping pyhon2 support with the next release remains the best option. Even better of course would be to keep the option for bugfix releases for 8.9 / 9.0. That would be a nice thing to have in general, but we could also just make an exception for this one release. -- 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/81d27008-9330-4f47-ae11-b65fd442cbba%40googlegroups.com.
