-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Add support for PEP 646 #87390
Comments
Since things are piling up, here's a quick record of what I think the remaining tasks are: (in approximate order of priority)
|
We also need to add to the What's New for 3.11. I volunteered to do that for all the typing PEPs.
Linking your #76300
I believe this uses the same mechanism as pickling, so shouldn't need more work. |
Done once #32103 is merged.
Done once #32159 is merged.
Will re-visit this now. |
@mrahtz @JelleZijlstra @serhiy-storchaka Is it okay if I unsubscribe from these conversations and let you all come up with a compromise? I feel that while we ought to have a policy formulated and mostly implemented by beta 1 (May 6), tweaks of both the policy and the implementation during the beta period until RC 1 (Aug/Sept?) should be allowable. |
@gvanrossum Fine with me. Godspeed with the rest of your work for this release :) |
Keeping track of things yet to do:
Decided against doing:
|
How much of the checklist above is still relevant? |
Thanks for the reminder! From a quick look, some of the items in the checklist are definitely still relevant. I'll try and find some time for this soon. |
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>. (cherry picked from commit cb95cc2) Co-authored-by: Matthew Rahtz <matthew.rahtz@gmail.com>
Friendly ping on this -- are the unchecked items on the checklist still to do, or is this issue ~complete now? :) |
Whoops, sorry - we finished #98267 last year but I completely forgot to update the checklist. I believe we can go ahead and close this now :) (though I can't seem to do this myself because the issue was created before the move to GitHub or something? Can you do it on your end?) |
No worries -- great to hear!
I sure can. Thanks for all the work you put into this, it was a marathon! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: