blob: 76b65a414774d098d93290ab74741cb129d260ce [file] [log] [blame]
Victor Stinner01adf062014-03-18 00:53:32 +01001****************************
2 What's New In Python 3.5
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.5, compared to 3.4.
49
50For full details, see the :source:`Misc/NEWS` file.
51
52.. note:: Prerelease users should be aware that this document is currently in
53 draft form. It will be updated substantially as Python 3.5 moves towards
54 release, so it's worth checking back even after reading earlier versions.
55
56
57.. seealso::
58
59 .. :pep:`4XX` - Python 3.5 Release Schedule
60
61
62Summary -- Release highlights
63=============================
64
65.. This section singles out the most important changes in Python 3.3.
66 Brevity is key.
67
68New syntax features:
69
70* None yet.
71
72New library modules:
73
74* None yet.
75
76New built-in features:
77
78* None yet.
79
80Implementation improvements:
81
Victor Stinner71430292014-03-18 01:18:21 +010082* When the ``LC_TYPE`` locale is the POSIX locale (``C`` locale),
83 :py:data:`sys.stdin` and :py:data:`sys.stdout` are now using the
84 ``surrogateescape`` error handler, instead of the ``strict`` error handler
85 (:issue:`19977`).
Victor Stinner01adf062014-03-18 00:53:32 +010086
87Significantly Improved Library Modules:
88
89* None yet.
90
91Security improvements:
92
93* None yet.
94
95Please read on for a comprehensive list of user-facing changes.
96
97
98.. PEP-sized items next.
99
100.. _pep-4XX:
101
102.. PEP 4XX: Virtual Environments
103.. =============================
104
105
106.. (Implemented by Foo Bar.)
107
108.. .. seealso::
109
110 :pep:`4XX` - Python Virtual Environments
111 PEP written by Carl Meyer
112
113
114
115
116Other Language Changes
117======================
118
119Some smaller changes made to the core Python language are:
120
121* None yet.
122
123
124
125New Modules
126===========
127
128.. module name
129.. -----------
130
131* None yet.
132
133
134Improved Modules
135================
136
Giampaolo Rodola'e09fb712014-04-04 15:34:17 +0200137* Different constants of :mod:`signal` module are now enumeration values using
138 the :mod:`enum` module. This allows meaningful names to be printed during
139 debugging, instead of integer “magic numbers”. (contribute by Giampaolo
140 Rodola' in :issue:`21076`)
141
Brett Cannon33a40002014-03-21 11:24:40 -0400142* :class:`xmlrpc.client.ServerProxy` is now a :term:`context manager`
143 (contributed by Claudiu Popa in :issue:`20627`).
Victor Stinner01adf062014-03-18 00:53:32 +0100144
Yury Selivanova5d63dd2014-03-27 11:31:43 -0400145* :class:`inspect.Signature` and :class:`inspect.Parameter` are now
146 picklable (contributed by Yury Selivanov in :issue:`20726`).
147
Yury Selivanovda396452014-03-27 12:09:24 -0400148* New class method :meth:`inspect.Signature.from_callable`, which makes
149 subclassing of :class:`~inspect.Signature` easier (contributed
150 by Yury Selivanov and Eric Snow in :issue:`17373`).
151
Brett Cannona04dbe42014-04-04 13:53:38 -0400152* :class:`importlib.util.LazyLoader` allows for the lazy loading of modules in
153 applications where startup time is paramount (contributed by Brett Cannon in
154 :issue:`17621`).
155
Victor Stinner01adf062014-03-18 00:53:32 +0100156
157Optimizations
158=============
159
160Major performance enhancements have been added:
161
162* None yet.
163
164
165Build and C API Changes
166=======================
167
168Changes to Python's build process and to the C API include:
169
170* None yet.
171
172
173Deprecated
174==========
175
176Unsupported Operating Systems
177-----------------------------
178
179* None yet.
180
181
182Deprecated Python modules, functions and methods
183------------------------------------------------
184
Brett Cannona77d0c32014-03-21 10:52:33 -0400185* The :mod:`formatter` module has now graduated to full deprecation and is still
186 slated for removal in Python 3.6.
Victor Stinner01adf062014-03-18 00:53:32 +0100187
188
189Deprecated functions and types of the C API
190-------------------------------------------
191
192* None yet.
193
194
195Deprecated features
196-------------------
197
198* None yet.
199
200
201Porting to Python 3.5
202=====================
203
204This section lists previously described changes and other bugfixes
205that may require changes to your code.
206
Benjamin Petersonee6bdc02014-03-20 18:00:35 -0500207* Before Python 3.5, a :class:`datetime.time` object was considered to be false
208 if it represented midnight in UTC. This behavior was considered obscure and
209 error-prone and has been removed in Python 3.5. See :issue:`13936` for full
210 details.