blob: 8a6b02179db176eb98e9c75bff88c1f6d93f5c68 [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
77
78Other Language Changes
79======================
80
Serhiy Storchaka578c3952020-05-26 18:43:38 +030081* Builtin and extension functions that take integer arguments no longer accept
82 :class:`~decimal.Decimal`\ s, :class:`~fractions.Fraction`\ s and other
83 objects that can be converted to integers only with a loss (e.g. that have
84 the :meth:`~object.__int__` method but do not have the
85 :meth:`~object.__index__` method).
86 (Contributed by Serhiy Storchaka in :issue:`37999`.)
Pablo Galindod4fe0982020-05-19 03:33:01 +010087
88
89New Modules
90===========
91
92* None yet.
93
94
95Improved Modules
96================
97
Huon Wilson8b626442020-05-23 00:18:51 +100098tracemalloc
99-----------
100
101Added :func:`tracemalloc.reset_peak` to set the peak size of traced memory
102blocks to the current size, to measure the peak of specific pieces of code.
103(Contributed by Huon Wilson in :issue:`40630`.)
Pablo Galindod4fe0982020-05-19 03:33:01 +0100104
105Optimizations
106=============
107
108
Pablo Galindod4fe0982020-05-19 03:33:01 +0100109Deprecated
110==========
111
112
Pablo Galindod4fe0982020-05-19 03:33:01 +0100113Removed
114=======
115
116
Pablo Galindod4fe0982020-05-19 03:33:01 +0100117Porting to Python 3.10
118======================
119
120This section lists previously described changes and other bugfixes
121that may require changes to your code.
122
123
Dong-hee Naad3252b2020-05-26 01:52:54 +0900124
125Build Changes
126=============
127
128
129C API Changes
130=============
131
132New Features
133------------
134
Serhiy Storchaka5f4b229d2020-05-28 10:33:45 +0300135 The result of :c:func:`PyNumber_Index` now always has exact type :class:`int`.
136 Previously, the result could have been an instance of a subclass of ``int``.
137 (Contributed by Serhiy Storchaka in :issue:`40792`.)
138
Dong-hee Naad3252b2020-05-26 01:52:54 +0900139
140Porting to Python 3.10
141----------------------
142
143* Since :c:func:`Py_TYPE()` is changed to the inline static function,
144 ``Py_TYPE(obj) = new_type`` must be replaced with ``Py_SET_TYPE(obj, new_type)``:
145 see :c:func:`Py_SET_TYPE()` (available since Python 3.9).
146 (Contributed by Dong-hee Na in :issue:`39573`.)
147
Victor Stinnerfe2978b2020-05-27 14:55:10 +0200148* Since :c:func:`Py_REFCNT()` is changed to the inline static function,
149 ``Py_REFCNT(obj) = new_refcnt`` must be replaced with ``Py_SET_REFCNT(obj, new_refcnt)``:
150 see :c:func:`Py_SET_REFCNT()` (available since Python 3.9).
151 (Contributed by Victor Stinner in :issue:`39573`.)
152
153* Since :c:func:`Py_SIZE()` is changed to the inline static function,
154 ``Py_SIZE(obj) = new_size`` must be replaced with ``Py_SET_SIZE(obj, new_size)``:
155 see :c:func:`Py_SET_SIZE()` (available since Python 3.9).
156 (Contributed by Victor Stinner in :issue:`39573`.)
Dong-hee Naad3252b2020-05-26 01:52:54 +0900157
158Removed
159-------