Description
Situation
At the moment, this project uses and supports Python 2.7. As we all know, Python 2.7 is going out of maintenance soon ("retire") and it's not clear what the project is going to do.
After disussing #160, we found out that the project doesn't have a clear statement or information regarding the retirement of Python 2.7 (neither in issues, README, nor documentation). Maybe I have missed something; in that case we can close this issue. 😉
We are currently lacking answers of the following questions:
- For how long do we want to support Python 2.7?
- Which semver version(s) still support Python 2.7?
- Do we want to have semver 3.x.y which supports only Python 3.x?
Suggested Solution
Whatever the project decides, we need to document it. 😉 What about the following approach?
- Add a short note, paragraph, section etc. about the retirement of Python 2.7 inside our README. Maybe even link to this issue.
- Focus in our documentation on Python3 only.
Apart from the documentation issues, I would also propose to indicate such a change with raising the major version of semver. For example:
- 2.x: would still contain the support for Python 2.7
- 3.x: would be the main line without support for Python 2.7 (in other words, >= Python 3.5 only)
Luckily, such major versions match with the Python version. 😉
Would that help?