-
Notifications
You must be signed in to change notification settings - Fork 71
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 version support policy #463
Comments
Python 4 doesn't seem to be on the horizon yet, and it might turn out to be a relatively minor increment (they don't follow semantic versioning). The Python team also seem to've learned from the 2->3 debacle; a new major release isn't likely to be on the same scale as that. All that said, it's useful for PySB users to have some certainty. I'd suggest N=2 years is reasonable. If Python 4 turns out to require only minor changes, we could choose to keep Python 3 support in the master branch as well, but I don't think that's something we can commit to until more details are known. |
Our Python version support policy is up on our website, and reproduced below:
|
As a follow-on to #414, we should establish an official policy on what versions of Python we will support. @alubbock suggested "three most recent minor versions" which today would mean 3.5, 3.6 and 3.7. That's fine with me. We should also decide how we'll handle Python major versions, e.g. if Python 4 ever happens. :) Maybe a LTS (long-term support) model, such as:
The text was updated successfully, but these errors were encountered: