Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.4k
gh-114099: Formalize Tier 3 status of iOS#118020
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think you are being a bit too modest here in theWhat's New entry. Rather thanhiding it under the Build Changes section, I think the work here is worthy of appearing in theNew Features section near the top with a reference to PEP 730, similar to the entries inthe 3.12 What's New. Yes, theWhat's New will be edited before the final release but it would be nice to get it in the right place now.
/me blushes As requested, I've bumped the iOS announcement up the page to the "New Features" section, presumptively adding a section header that will also be able to accomodate an Android/PEP 738 announcement (which I believe is getting fairly close to hitting tier 3 status). |
Uh oh!
There was an error while loading.Please reload this page.
All the patches required for iOS support have been merged, and abuildbot is now active and passing.
I believe this completes the work required for PEP 730; so this PR adds a news entry, and adds myself to the ACKS list.
Fixes#114099.
📚 Documentation preview 📚:https://cpython-previews--118020.org.readthedocs.build/