--
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...@googlegroups.com.
To post to this group, send email to scikit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CABDkGQmJyoCWrBu%3DpV41V2-dJD0wp6mrvrqHuaYCDeYmXYeW2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Note that end of life for Python 2.x is actually now-ish, and that support is being offered exactly so that industry and others have time to switch over. It does not mean that folks should aim at using 2.7 until 2020!
Maintaining support for an old version of Python carries a maintenance burden that I'd like to avoid if possible.
Also, once our dependencies such as numpy, scipy or matplotlib make the move, we can theoretically keep supporting 2.x for a while longer, but not *much* longer.
Folks in industry often run on platforms such as Anaconda, where this will probably be a non issue by then. I'm more concerned about big clusters, University labs, etc. But even there we are now able to provide both virtual environments or Conda envs much more easily than before.
Stéfan
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CAP0v5tn%2BojdyKOrzs8LS8_YhRHTCv1ar7zudZAVLBaLkAJaCGw%40mail.gmail.com.
Even though official support for 2.7 will be dropped on the Python side, my feeling is that it will stick around in official linux repositories for quite some time longer. Especially on clusters etc., as you mentioned. I would suggest to drop 2.7 support as soon as Numpy/Scipy drops it - this is an upper bound as we depend on it and, at the same time, numpy/scipy are important enough libraries that should also convince the last developer to make the switch to 3.x.
At the moment, can you estimate the cost of supporting Python 2.7, in
terms of additional code? (I would say that testing 2.7 in CI is not a
true cost, since it represents server time and not human time)
> It's probably not terribly much, but it does prohibit us from making use of
> newer language features as they develop.
Any pointer about such new features so that ignorant people like myself
can educate themselves :-D?
> I should emphasize that I think it's perfectly reasonable to keep
> supporting an older release of scikit-image for 2.7, just not the
> latest release.
Of course. It's possible that in 2020 we'll have reached a "stationary
state" as NumPy, and that new releases will mostly be about bug fixes and
improved documentation. But we're still on a fast growing curve, so it's
hard to know.
Just a pointer : Ubuntu 16.04 has officially removed Python 2 from the distribution. So yes, *people will be* moving to Python 3 now.
--
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...@googlegroups.com.
To post to this group, send email to scikit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CABDkGQm_SE8fjU1ZiUg1kWne1eLTicjvtV14Bhp1x8fOupOQNA%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CANpJW-URfDAKKzmbeLQz5%3DksxjJ8QbFCU2Hdm4bedZ2zx1AAAw%40mail.gmail.com.
--
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...@googlegroups.com.
To post to this group, send an email to scikit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/20160520141800.GD3583487%40phare.normalesup.org.
On May 20, 2016 07:30, "Michael Sarahan" <msar...@gmail.com> wrote:
> I don't think this is a concern for cython or scikit-image, but many people at bumping into the language support limit in the C++11 sense with Python 2.7 on Windows. Since VS 2008 is the de-facto standard compiler for Python 2.7, people are unable to use C++11 code in modules for Python 2.7. Some people use newer compilers anyway, which sometimes works, but is mixing runtimes, and can lead to bugs or crashes. Many people would like to support Python 2.7 using a different compiler for the whole ecosystem. One example is Ilastik, by folks at HHMI, using VS 2012 to have a custom stack: https://github.com/ilastik/ilastik-build-conda
I think getting mingwpy finished and polished is probably an easier solution for this problem than forking the entire py27-on-windows ecosystem :-)
-n
--
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...@googlegroups.com.
To post to this group, send email to scikit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/CAPJVwB%3DjRQtHn9Xj0xwv3hxtDsjBvKYtJTB38ewBuZ84cNR4xw%40mail.gmail.com.
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.
--
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...@googlegroups.com.
To post to this group, send email to scikit...@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.