-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python 2 deprecation! #303
Comments
related to #302, where python filesystem 2 demands unicode file path in python 2. |
https://travis-ci.org/moremoban/moban/jobs/562319080 unicode break flake8 |
pysetup can be considered https://pysetup.readthedocs.io/en/latest/tutorial.html#installing-pysetup |
|
|
there are python 2 files for GitPython. So not sure why pypy2.7-6.0 would complain |
We should cut a branch for Python 2 support and do a final release with Python 2 support, before removing support. We can use multiple pins, like done with ruamel.yaml, to install older versions that support Python 2 only when required. |
Please note this thread too: PyFilesystem/pyfilesystem2#317 |
this will be a priority in 0.7.0, in which python 3.7 only codes will be introduced, such as typing, f-string and data classes. multi-processing via asyncio are under consideration too. |
I dont see a problem with py27 deprecation. If desupporting an old Python, please ensure that the setup.py uses |
Shall we drop python 2 support beyond 2020?
The text was updated successfully, but these errors were encountered: