Drop Python 2 support in PyScaffold v3.1 #177
Labels
enhancement
New feature or request
Milestone
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 ;-) |
abravalheri
added a commit
to abravalheri/pyscaffold
that referenced
this issue
Jun 18, 2018
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. |
abravalheri
added a commit
to abravalheri/pyscaffold
that referenced
this issue
Jun 18, 2018
The old format is not valid anymore. Additionally remove any python 2.7 env (not supported), see pyscaffold#177.
FlorianWilhelm
pushed a commit
that referenced
this issue
Jun 18, 2018
The old format is not valid anymore. Additionally remove any python 2.7 env (not supported), see #177.
Merged
|
Since the |
|
Unfortunately we have to wait 3.6 to be the base line to use f-strings 😝 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
setuptoolsthe 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: