blob: 98a231f80aaf20b662916b8475930ecec42af459 [file] [log] [blame]
Pablo Galindod4fe0982020-05-19 03:33:01 +01001****************************
2 What's New In Python 3.10
3****************************
4
5:Release: |release|
6:Date: |today|
7
8.. Rules for maintenance:
9
10 * Anyone can add text to this document. Do not spend very much time
11 on the wording of your changes, because your text will probably
12 get rewritten to some degree.
13
14 * The maintainer will go through Misc/NEWS periodically and add
15 changes; it's therefore more important to add your changes to
16 Misc/NEWS than to this file.
17
18 * This is not a complete list of every single change; completeness
19 is the purpose of Misc/NEWS. Some changes I consider too small
20 or esoteric to include. If such a change is added to the text,
21 I'll just remove it. (This is another reason you shouldn't spend
22 too much time on writing your addition.)
23
24 * If you want to draw your new text to the attention of the
25 maintainer, add 'XXX' to the beginning of the paragraph or
26 section.
27
28 * It's OK to just add a fragmentary note about a change. For
29 example: "XXX Describe the transmogrify() function added to the
30 socket module." The maintainer will research the change and
31 write the necessary text.
32
33 * You can comment out your additions if you like, but it's not
34 necessary (especially when a final release is some months away).
35
36 * Credit the author of a patch or bugfix. Just the name is
37 sufficient; the e-mail address isn't necessary.
38
39 * It's helpful to add the bug/patch number as a comment:
40
41 XXX Describe the transmogrify() function added to the socket
42 module.
43 (Contributed by P.Y. Developer in :issue:`12345`.)
44
45 This saves the maintainer the effort of going through the Mercurial log
46 when researching a change.
47
48This article explains the new features in Python 3.10, compared to 3.9.
49
Ned Deily29251b72020-05-19 07:39:29 -040050For full details, see the :ref:`changelog <changelog>`.
Pablo Galindod4fe0982020-05-19 03:33:01 +010051
52.. note::
53
54 Prerelease users should be aware that this document is currently in draft
55 form. It will be updated substantially as Python 3.10 moves towards release,
56 so it's worth checking back even after reading earlier versions.
57
58
59Summary -- Release highlights
60=============================
61
62.. This section singles out the most important changes in Python 3.10.
63 Brevity is key.
64
65
66.. PEP-sized items next.
67
68
69
70New Features
71============
72
73
74
75Other Language Changes
76======================
77
78
79
80New Modules
81===========
82
83* None yet.
84
85
86Improved Modules
87================
88
Huon Wilson8b626442020-05-23 00:18:51 +100089tracemalloc
90-----------
91
92Added :func:`tracemalloc.reset_peak` to set the peak size of traced memory
93blocks to the current size, to measure the peak of specific pieces of code.
94(Contributed by Huon Wilson in :issue:`40630`.)
Pablo Galindod4fe0982020-05-19 03:33:01 +010095
96Optimizations
97=============
98
99
Pablo Galindod4fe0982020-05-19 03:33:01 +0100100Deprecated
101==========
102
103
Pablo Galindod4fe0982020-05-19 03:33:01 +0100104Removed
105=======
106
107
Pablo Galindod4fe0982020-05-19 03:33:01 +0100108Porting to Python 3.10
109======================
110
111This section lists previously described changes and other bugfixes
112that may require changes to your code.
113
114
Dong-hee Naad3252b2020-05-26 01:52:54 +0900115
116Build Changes
117=============
118
119
120C API Changes
121=============
122
123New Features
124------------
125
126
127Porting to Python 3.10
128----------------------
129
130* Since :c:func:`Py_TYPE()` is changed to the inline static function,
131 ``Py_TYPE(obj) = new_type`` must be replaced with ``Py_SET_TYPE(obj, new_type)``:
132 see :c:func:`Py_SET_TYPE()` (available since Python 3.9).
133 (Contributed by Dong-hee Na in :issue:`39573`.)
134
135
136Removed
137-------