PEP 11: Add note about interpreting current Windows release #3617
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
hugovk
changed the title
|
I'm not sure exactly who needs to approve this (it's probably not Brett). There have been a few acks in Discord, and no complaints on python/cpython#113723, so maybe just allow a week or two for someone to scream. |
|
This looks sensible to me. We can always modify it forward if somebody does scream. |
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.
Just proposed text right now for discussion, but as the text of the policy requires a bit of interpretation (since Microsoft changes their lifecycle and set of releases frequently), I think it's worth writing our current intention in here.
📚 Documentation preview 📚: https://pep-previews--3617.org.readthedocs.build/