blob: 629909b79e2aa04f04e7097cee2d68b67ecae03a [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
Niklas Fiekas8bd216d2020-05-29 18:28:02 +020073* The :class:`int` type has a new method :meth:`int.bit_count`, returning the
74 number of ones in the binary expansion of a given integer, also known
75 as the population count. (Contributed by Niklas Fiekas in :issue:`29882`.)
Pablo Galindod4fe0982020-05-19 03:33:01 +010076
Dennis Sweeney3ee0e482020-06-12 13:19:25 -040077* The views returned by :meth:`dict.keys`, :meth:`dict.values` and
78 :meth:`dict.items` now all have a ``mapping`` attribute that gives a
79 :class:`types.MappingProxyType` object wrapping the original
80 dictionary. (Contributed by Dennis Sweeney in :issue:`40890`.)
81
Pablo Galindod4fe0982020-05-19 03:33:01 +010082
83Other Language Changes
84======================
85
Serhiy Storchaka578c3952020-05-26 18:43:38 +030086* Builtin and extension functions that take integer arguments no longer accept
87 :class:`~decimal.Decimal`\ s, :class:`~fractions.Fraction`\ s and other
88 objects that can be converted to integers only with a loss (e.g. that have
89 the :meth:`~object.__int__` method but do not have the
90 :meth:`~object.__index__` method).
91 (Contributed by Serhiy Storchaka in :issue:`37999`.)
Pablo Galindod4fe0982020-05-19 03:33:01 +010092
93
94New Modules
95===========
96
97* None yet.
98
99
100Improved Modules
101================
102
Pablo Galindod4fe0982020-05-19 03:33:01 +0100103Optimizations
104=============
105
106
Pablo Galindod4fe0982020-05-19 03:33:01 +0100107Deprecated
108==========
109
110
Pablo Galindod4fe0982020-05-19 03:33:01 +0100111Removed
112=======
113
114
Pablo Galindod4fe0982020-05-19 03:33:01 +0100115Porting to Python 3.10
116======================
117
118This section lists previously described changes and other bugfixes
119that may require changes to your code.
120
121
Dong-hee Naad3252b2020-05-26 01:52:54 +0900122
123Build Changes
124=============
125
126
127C API Changes
128=============
129
130New Features
131------------
132
Serhiy Storchaka5f4b229d2020-05-28 10:33:45 +0300133 The result of :c:func:`PyNumber_Index` now always has exact type :class:`int`.
134 Previously, the result could have been an instance of a subclass of ``int``.
135 (Contributed by Serhiy Storchaka in :issue:`40792`.)
136
Dong-hee Naad3252b2020-05-26 01:52:54 +0900137
138Porting to Python 3.10
139----------------------
140
141* Since :c:func:`Py_TYPE()` is changed to the inline static function,
142 ``Py_TYPE(obj) = new_type`` must be replaced with ``Py_SET_TYPE(obj, new_type)``:
Victor Stinnerdc24b8a2020-06-04 22:10:43 +0200143 see :c:func:`Py_SET_TYPE()` (available since Python 3.9). For backward
144 compatibility, this macro can be used::
145
146 #if PY_VERSION_HEX < 0x030900A4
147 # define Py_SET_TYPE(obj, type) ((Py_TYPE(obj) = (type)), (void)0)
148 #endif
149
Dong-hee Naad3252b2020-05-26 01:52:54 +0900150 (Contributed by Dong-hee Na in :issue:`39573`.)
151
Victor Stinnerfe2978b2020-05-27 14:55:10 +0200152* Since :c:func:`Py_REFCNT()` is changed to the inline static function,
153 ``Py_REFCNT(obj) = new_refcnt`` must be replaced with ``Py_SET_REFCNT(obj, new_refcnt)``:
Victor Stinnerdc24b8a2020-06-04 22:10:43 +0200154 see :c:func:`Py_SET_REFCNT()` (available since Python 3.9). For backward
155 compatibility, this macro can be used::
156
157 #if PY_VERSION_HEX < 0x030900A4
158 # define Py_SET_REFCNT(obj, refcnt) ((Py_REFCNT(obj) = (refcnt)), (void)0)
159 #endif
160
Victor Stinnerfe2978b2020-05-27 14:55:10 +0200161 (Contributed by Victor Stinner in :issue:`39573`.)
162
163* Since :c:func:`Py_SIZE()` is changed to the inline static function,
164 ``Py_SIZE(obj) = new_size`` must be replaced with ``Py_SET_SIZE(obj, new_size)``:
Victor Stinnerdc24b8a2020-06-04 22:10:43 +0200165 see :c:func:`Py_SET_SIZE()` (available since Python 3.9). For backward
166 compatibility, this macro can be used::
167
168 #if PY_VERSION_HEX < 0x030900A4
169 # define Py_SET_SIZE(obj, size) ((Py_SIZE(obj) = (size)), (void)0)
170 #endif
171
Victor Stinnerfe2978b2020-05-27 14:55:10 +0200172 (Contributed by Victor Stinner in :issue:`39573`.)
Dong-hee Naad3252b2020-05-26 01:52:54 +0900173
Victor Stinner59d3dce2020-06-02 14:03:25 +0200174* Calling :c:func:`PyDict_GetItem` without :term:`GIL` held had been allowed
175 for historical reason. It is no longer allowed.
176 (Contributed by Victor Stinner in :issue:`40839`.)
177
Dong-hee Naad3252b2020-05-26 01:52:54 +0900178Removed
179-------