-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Drop Python 2 support in PyScaffold v3.1 #177
Comments
To be sincere, since the test suite is intrinsically broken with 2.7, all the last changes might be incompatible anyway... |
Okay, sounds like we have a decision then ;-) |
The old format is not valid anymore. Additionally remove any python 2.7 env (not supported), see pyscaffold#177.
Since we have never had Python 2 support in version 3.0 we can drop it in version 3.1 officially without violating semantic version. I wouldn't want to wait for version 4.0 for that. |
The old format is not valid anymore. Additionally remove any python 2.7 env (not supported), see pyscaffold#177.
The old format is not valid anymore. Additionally remove any python 2.7 env (not supported), see #177.
Since the |
Unfortunately we have to wait 3.6 to be the base line to use f-strings 😝 |
PyScaffold is a tool for creating new Python projects and Python 3 surely has been for quite a while the right version to start a new project. Also due the a bug in
setuptools
the current version 3.0 of PyScaffold has no Python 2 support right now and there were no complaints about this.We could officially drop the Python 2 support in PyScaffold 3.1 and get rid of
six
, unnecessary__future__
imports in templates and the code of PyScaffold itself. This would clean things up.The text was updated successfully, but these errors were encountered: