Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Sunsetting Python 2 support #164
We should set a timeline for dropping Python 2 support per https://python3statement.org
We barely test
This might have implications for the conda and PyPI deployments - is there a way we could let those vendors know not to allow installing
Looking at the web page, there's two ways we can do this. Like most of the projects, we can just drop support outright (either now or on 1 Jan 2020), or we can keep an older version of vtki around with LTS.
I'm leaning towards just dropping support outright. I have some dependent projects that are still barely Py2.7 compatible and I'd really like the companies using them to abandon 2.7 altogether. Having
As for PyPi and conda, we can simply add in the following in setup.py (idea from stackoverflow)
import sys if sys.version_info.major < 3: raise RuntimeError('Only Python 3.4+ supported. ' + 'Please install a modern version of Python')
That will stop anyone from trying to install using an unsupported version of Python outright. As far as I know, the
Me too - it's become quite an annoyance to write hooks and debug 2.7 errors.
Also, thanks for looking into ways to enforce a Python 3 install! I'll handle all of the anaconda stuff when we decide to move forward with this.
I too have PVGeo still supporting 2.7 as ParaView uses Python 2.7. Kitware has a plan in the works for switching to Python 3 but who knows when that will play out.
On the note of your other packages and mine still needed on Python 2.7, I think the core API of
Note that I have disabled testing for Python 2.7 on Travis in #176
I'm tired of dealing with Python 2 issues... and we barely tested the library on 2.7
If we need to add this back, we can set up build matrices with allowed failures. I started doing this a while back on the