SPEC 1: mention PEP 810 and plans for sunsetting the SPEC - #433
Closed
neutrinoceros wants to merge 1 commit into
Closed
neutrinoceros wants to merge 1 commit into
neutrinoceros wants to merge 1 commit into
Conversation
neutrinoceros
force-pushed
the
spec01/pep810-mention
branch
from
September 21, 2026 15:21
60bcd6c to
e6509db
Compare
lucascolley
approved these changes
Sep 21, 2026
Member
|
@jarrodmillman had a PR in work to update the SPEC1 text, I would be very much in favour of having that one in than this one. |
Member
|
Closing this in favour of #434 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Close #413
not sure about the exact phrasing or formatting, but this looks like the gist of it.