Add explicit deprecation and python support policies #444
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Deprecation policy is based on pip's: https://pip.pypa.io/en/stable/development/release-process/#deprecation-policy Python support follows NEP 29: https://numpy.org/neps/nep-0029-deprecation_policy.html Fixes #398
jfrost-mo
force-pushed
the
398_deprication_policy
branch
from
892b7f2
to
9ab0971
Compare
Sylviabohnenstengel
approved these changes
Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deprecation policy is based on pip's:
https://pip.pypa.io/en/stable/development/release-process/#deprecation-policy
Python support follows NEP 29:
https://numpy.org/neps/nep-0029-deprecation_policy.html
Incidentally this means we should drop python 3.9 in the April release. (#445)