|
1 | 1 |
|
| 2 | +**************************** |
| 3 | + What's New In Python 3.12 |
| 4 | +**************************** |
| 5 | + |
| 6 | +:Release: |release| |
| 7 | +:Date: |today| |
| 8 | + |
| 9 | +.. Rules for maintenance: |
| 10 | +
|
| 11 | + * Anyone can add text to this document. Do not spend very much time |
| 12 | + on the wording of your changes, because your text will probably |
| 13 | + get rewritten to some degree. |
| 14 | +
|
| 15 | + * The maintainer will go through Misc/NEWS periodically and add |
| 16 | + changes; it's therefore more important to add your changes to |
| 17 | + Misc/NEWS than to this file. |
| 18 | +
|
| 19 | + * This is not a complete list of every single change; completeness |
| 20 | + is the purpose of Misc/NEWS. Some changes I consider too small |
| 21 | + or esoteric to include. If such a change is added to the text, |
| 22 | + I'll just remove it. (This is another reason you shouldn't spend |
| 23 | + too much time on writing your addition.) |
| 24 | +
|
| 25 | + * If you want to draw your new text to the attention of the |
| 26 | + maintainer, add 'XXX' to the beginning of the paragraph or |
| 27 | + section. |
| 28 | +
|
| 29 | + * It's OK to just add a fragmentary note about a change. For |
| 30 | + example: "XXX Describe the transmogrify() function added to the |
| 31 | + socket module." The maintainer will research the change and |
| 32 | + write the necessary text. |
| 33 | +
|
| 34 | + * You can comment out your additions if you like, but it's not |
| 35 | + necessary (especially when a final release is some months away). |
| 36 | +
|
| 37 | + * Credit the author of a patch or bugfix. Just the name is |
| 38 | + sufficient; the e-mail address isn't necessary. |
| 39 | +
|
| 40 | + * It's helpful to add the bug/patch number as a comment: |
| 41 | +
|
| 42 | + XXX Describe the transmogrify() function added to the socket |
| 43 | + module. |
| 44 | + (Contributed by P.Y. Developer in :issue:`12345`.) |
| 45 | +
|
| 46 | + This saves the maintainer the effort of going through the Mercurial log |
| 47 | + when researching a change. |
| 48 | +
|
| 49 | +This article explains the new features in Python 3.12, compared to 3.11. |
| 50 | + |
| 51 | +For full details, see the :ref:`changelog <changelog>`. |
| 52 | + |
| 53 | +.. note:: |
| 54 | + |
| 55 | + Prerelease users should be aware that this document is currently in draft |
| 56 | + form. It will be updated substantially as Python 3.12 moves towards release, |
| 57 | + so it's worth checking back even after reading earlier versions. |
| 58 | + |
| 59 | + |
| 60 | +Summary -- Release highlights |
| 61 | +============================= |
| 62 | + |
| 63 | +.. This section singles out the most important changes in Python 3.12. |
| 64 | + Brevity is key. |
| 65 | +
|
| 66 | +
|
| 67 | +.. PEP-sized items next. |
| 68 | +
|
| 69 | +Important deprecations, removals or restrictions: |
| 70 | + |
| 71 | +* :pep:`623`, Remove wstr from Unicode |
2 | 72 |
|
3 | 73 |
|
4 | 74 | New Features
|
|
0 commit comments