René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"List and document remaining significant PEPs in What's New in 3.11","articleBody":"As discussed with @pablogsal , meta-issue to add the significant PEPs not yet added to the summary section of the [What's New in Python 3.11](https://docs.python.org/3.12/whatsnew/3.11.html), as well as PEPs that are not documented in the body of the What's New but probably should be.\r\n\r\nSpecifically, the PEPs not currently mentioned in the Summary - Release Highlights section are (written with a non-canonical `-` so GitHub will link them):\r\n\r\n- PEP-594 Removing dead stdlib batteries\r\n- PEP-624 Remove Py_UNICODE encoder APIs\r\n- PEP-657 Fine-grained error locations\r\n- PEP-670 Macros to Functions in the C API\r\n- PEP-678 Enriching exceptions with notes\r\n- PEP-680: Tomllib\r\n- PEP-681 Dataclass transforms\r\n- PEP-682 Format specifier for signed zero (?)\r\n\r\nThese will be added to the relevant lists as appropriate, following the mold of the [Python 3.10 What's New](https://docs.python.org/3.12/whatsnew/3.10.html)\r\n\r\n- [x] I've opened #95916 to do so. Edit: Merged!\r\n\r\nMost 3.11 PEPs are already described in other What's New sections, but a few are conspicuously missing and should probably be documented somewhere. I've cross referenced this with the PEP API, as well as Accepted/Final PEPs that were not tagged with a Python-Version (notably, PEP 654 was lacking it, which I also fixed):\r\n\r\n* [x] PEP-624 _Remove Py_UNICODE encoder APIs_ contains an [Alternative APIs section](https://peps.python.org/pep-0624/#alternative-apis) that would be useful for porting, but is not mentioned at all anywhere in What's New. Documenting the change and migration guidance was a [condition of the PEP's acceptance by the SC](https://mail.python.org/archives/list/python-dev@python.org/message/DR6YTABJ2UHC2HB2EY7R6NJO3OKXNPJN/), so it seems we should list those APIs under the `Removed` section and add the migration guidance under the `C API Changes` -\u003e `Porting to Python 3.11` subsection. ~@methane any objections if I go ahead with that, or would you like to do it yourself (I can proofread as needed)~\r\n  * I went ahead and opened #96016 \r\n\r\n* [x] PEP-654 _Exception Groups and except*_ _is_ listed in the Summary, but does not appear to be discussed at all in the body of the What's New, which it presumably should as it is a major new feature (and its related PEP 678 _is_ documented under New Features, but is _not_ listed in the Summary). ~@iritkatriel @1st1 @gvanrossum you're listed as the authors; would one of you like to write a summary, or do you want me to draft something for your (and @pablogsal 's) review?~ Done, thanks @iritkatriel !\r\n    * @iritkatriel opened as #95937 \r\n    * Related: #95976 \r\n\r\n* [x] PEP-670 _Convert Macros to Functions in the Python C API_ isn't mentioned anywhere; the intention with the specific PEP appears to be to avoid any backward compat impacts and be mostly transparent to users, but there is one significant change: With the limited ABI set to \u003e=3.11, callers will need to cast arguments to their expected values. @erlend-aasland @vstinner , should at least this (and maybe a mention of the broader change) be including in C API Changes -\u003e Porting to Python 3.11 subsection?\r\n    * On the suggestion of @erlend-aasland , I've opened #98315 to finally implement this\r\n\r\nThen, once those are dealt with, we should finally:\r\n\r\n* [x] Link the relevant What's New sections and other index targets in the respective summary items, so readers can quickly jump to more information about them\r\n    * Opened as PR #98416\r\n\r\nRelated: #95913 ","author":{"url":"https://github.com/CAM-Gerlach","@type":"Person","name":"CAM-Gerlach"},"datePublished":"2022-08-12T06:05:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":14},"url":"https://github.com/95914/cpython/issues/95914"}