| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
(parser; assignment expr; exceptions; GC; builtins; modules; other)
Is the order chosen by a general idea of general importance/interest? Would using these as subheadings be useful? |
Sorry, something went wrong.
|
Somewhat arbitrary, but inspired by the order in the relese highlights. The one I was unsure about was where to put GC -- syntax changes make sense going first; the annotation expression change is a relaxation/change to the language; then library (builtins). I'd probably not go with headings, as the list is short enough; and having a (loose) order helps readers implicitly group items. A |
Sorry, something went wrong.
|
Thanks @AA-Turner for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
|
Sorry, @AA-Turner and @hugovk, I could not cleanly backport this to 3.12 due to a conflict. |
Sorry, something went wrong.
… Changes (pythonGH-109836). (cherry picked from commit 86e7c61) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
GH-109880 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--109836.org.readthedocs.build/