NEP 29 > SPEC 0 in dependency policy #29744
Merged
Conversation
This file contains hidden or 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
timhoffm
approved these changes
Mar 12, 2025
|
This probably should get more discussion, SPEC0 is not identical to NEP29 (SPEC0 has shorter support windows). |
|
Ah, my bad for not checking - this does indeed make the text below inconsistent with SPEC 0. I'll open a PR revert this, and then later open a new PR proposing we move to SPEC 0 and outlining in detail how that would change the current policies. |
1 task
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.
PR summary
Since NEP 29 is superseded by SPEC 0, update the link in our dependency policy.
PR checklist