-
Notifications
You must be signed in to change notification settings - Fork 63
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
End Of Life for Python 2.7 - Pyment will run uder Python 3.6+ #97
Comments
My system's default install is still Python 2.7, so it was more convenient for me to change the (literally) 3 places in the codebase that require Python 3. I would keep the Python 2.7 compliance unless there is a feature that requires it. |
Nobody cares for systems which can't feature python 3, and python 2 has no support anymore, nobody should write (new) python 2 code - so can be expected that development systems have python 3 anyway. |
This is a nice ideal, but it isn’t the reality for industry systems that
need to work with legacy codebases. One can ridicule old systems for their
age, but it does not change the fact that they exist, and there are valid
reasons for not upgrading (yet).
I think it is not a problem to stop supporting Python 2.7 as the target of Pyment is source code that could be updated in a different context than the one where it is used.
|
As I said, nobody cares. Pyment is no longer able to run under Python 2, as it should. |
Hi there,
As Python 2.7 has reached end of life last year, I plan to stop supporting running Pyment using it in next release v0.4.0 in few days. And furthermore, I will use f-strings that were introduced in Python 3.6, so Pyment will need Python at least Python 3.6 to run.
But I'd like to know if some people would consider important supporting it?
The text was updated successfully, but these errors were encountered: