For what it's worth, I strongly support the statement, and would prefer to drop 2.7 support much earlier. This does *not* mean ignoring people submitting 2.7 bug reports. It means that, like Python itself, *new* versions would not support Py2.7. Bug fixes would be ported to e.g. the 0.13.x branch. This in no way interferes people with systems that "just work" and who understandably don't want to risk breaking them.
Juan. On Mon, Jul 4, 2016 at 7:12 PM, Josh Warner <silvertrumpet...@gmail.com> wrote: > I think we should support 2.7 through end-of-life. 2020 sounds right. > > There are a tremendous amount of systems out there still running 2.7. I > know more than one lab which standardized on 2.7 years ago, and while we're > evaluating the move to 3.x it won't be without major pains. Small, niche > packages which work perfectly under 2.7 break in 3.x, and they may or may > not be maintained. It only takes a couple of these to render lab equipment > with price tags in the 6 figures buggy, problematic, or useless in 3.x. > This is problematic when you want a consistent Python experience across a > lab or team, but certain pieces just won't work in 3.x. > > Sounding the trumpets is appropriate, as 2.7 won't be around forever. > Quarterly or bi-annually it would be reasonable to send out a reminder. > Three years sounds like a long time, but that's about right for this kind > of transition. > > On Monday, July 4, 2016 at 4:55:34 AM UTC-5, Thomas Kluyver wrote: >> >> On 4 July 2016 at 10:47, François Boulogne <fboulo...@sciunto.org> wrote: >> >>> Does it mean that all new version of those libraries will support >>> python2.7 until 2020 or just that you can release a bugfix to already >>> released version supporting 2.7? >>> >>> If it's the first option, it means we can't use python3 features before >>> 2020 and we will be "in late" with these features. >>> >> >> The statement doesn't commit projects to support 2.7 until any specific >> date - scikit-bio already went Python 3 only with its release last month, >> for instance. We're agreeing to end Python 2 support by 2020, but projects >> are welcome to do it earlier than that. >> >> For IPython, we're planning for the 6.0 feature release (some time in >> 2017) to be Python 3 only, while we'll make bugfix releases of the 5.x >> series for longer than normal to support users on Python 2. >> > -- > You received this message because you are subscribed to the Google Groups > "scikit-image" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to scikit-image+unsubscr...@googlegroups.com. > To post to this group, send email to scikit-image@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/scikit-image/dc739979-e63f-4ce0-849b-66f8a659c8fc%40googlegroups.com > <https://groups.google.com/d/msgid/scikit-image/dc739979-e63f-4ce0-849b-66f8a659c8fc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscr...@googlegroups.com. To post to this group, send an email to scikit-image@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CA%2BJHcKRwRfjgYfuouzf63J083JSU2SzMorEQ5F4LntieWCtwPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
