1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
|
****************************
What's New In Python 3.4
****************************
.. :Author: Someone <email>
(uncomment if there is a principal author)
.. Rules for maintenance:
* Anyone can add text to this document, but the maintainer reserves the
right to rewrite any additions. In particular, for obscure or esoteric
features, the maintainer may reduce any addition to a simple reference to
the new documentation rather than explaining the feature inline.
* While the maintainer will periodically go through Misc/NEWS
and add changes, it's best not to rely on this. We know from experience
that any changes that aren't in the What's New documentation around the
time of the original release will remain largely unknown to the community
for years, even if they're added later. We also know from experience that
other priorities can arise, and the maintainer will run out of time to do
updates - in such cases, end users will be much better served by partial
notifications that at least give a hint about new features to
investigate.
* This is not a complete list of every single change; completeness
is the purpose of Misc/NEWS. The What's New should focus on changes that
are visible to Python *users* and that *require* a feature release (i.e.
most bug fixes should only be recorded in Misc/NEWS)
* PEPs should not be marked Final until they have an entry in What's New.
A placeholder entry that is just a section header and a link to the PEP
(e.g ":pep:`397` has been implemented") is acceptable. If a PEP has been
implemented and noted in What's New, don't forget to mark it as Final!
* If you want to draw your new text to the attention of the
maintainer, add 'XXX' to the beginning of the paragraph or
section.
* It's OK to add just a very brief note about a change. For
example: "The :ref:`~socket.transmogrify()` function was added to the
:mod:`socket` module." The maintainer will research the change and
write the necessary text (if appropriate). The advantage of doing this
is that even if no more descriptive text is ever added, readers will at
least have a notification that the new feature exists and a link to the
relevant documentation.
* You can comment out your additions if you like, but it's not
necessary (especially when a final release is some months away).
* Credit the author of a patch or bugfix. Just the name is
sufficient; the e-mail address isn't necessary.
* It's helpful to add the bug/patch number as a comment:
The :ref:`~socket.transmogrify()` function was added to the
:mod:`socket` module. (Contributed by P.Y. Developer in :issue:`12345`.)
This saves the maintainer the effort of going through the Mercurial log
when researching a change.
* Cross referencing tip: :ref:`mod.attr` will display as ``mod.attr``,
while :ref:`~mod.attr` will display as ``attr``.
This article explains the new features in Python 3.4, compared to 3.3.
.. Python 3.4 was released on TBD.
For full details, see the
`changelog <http://docs.python.org/3.4/whatsnew/changelog.html>`_.
.. note:: Prerelease users should be aware that this document is currently in
draft form. It will be updated substantially as Python 3.4 moves towards
release, so it's worth checking back even after reading earlier versions.
.. seealso::
.. :pep:`4XX` - Python 3.4 Release Schedule
Summary -- Release highlights
=============================
.. This section singles out the most important changes in Python 3.4.
Brevity is key.
New syntax features:
* None yet.
New library modules:
* None yet.
New built-in features:
* None yet.
Implementation improvements:
* A more efficient :mod:`marshal` format <http://bugs.python.org/issue16475>.
Significantly Improved Library Modules:
* SHA-3 (Keccak) support for :mod:`hashlib`.
* TLSv1.1 and TLSv1.2 support for :mod:`ssl`.
Security improvements:
* None yet.
Please read on for a comprehensive list of user-facing changes.
.. PEP-sized items next.
.. _pep-4XX:
.. PEP 4XX: Example PEP
.. ====================
.. (Implemented by Foo Bar.)
.. .. seealso::
:pep:`4XX` - Example PEP
PEP written by Example Author
Other Language Changes
======================
Some smaller changes made to the core Python language are:
* Unicode database updated to UCD version 6.2.
New Modules
===========
.. module name
.. -----------
* None yet.
Improved Modules
================
doctest
-------
Added ``FAIL_FAST`` flag to halt test running as soon as the first failure is
detected. (Contributed by R. David Murray and Daniel Urban in :issue:`16522`.)
wave
----
The :meth:`~wave.getparams` method now returns a namedtuple rather than a
plain tuple. (Contributed by Claudiu Popa in :issue:`17487`.)
Optimizations
=============
Major performance enhancements have been added:
* The UTF-32 decoder is now 3x to 4x faster.
Build and C API Changes
=======================
Changes to Python's build process and to the C API include:
* None yet.
Deprecated
==========
Unsupported Operating Systems
-----------------------------
* None yet.
Deprecated Python modules, functions and methods
------------------------------------------------
* :meth:`difflib.SequenceMatcher.isbjunk` and
:meth:`difflib.SequenceMatcher.isbpopulur`: use ``x in sm.bjunk`` and
``x in sm.bpopular``, where sm is a :class:`~difflib.SequenceMatcher` object.
Deprecated functions and types of the C API
-------------------------------------------
* None yet.
Deprecated features
-------------------
* None yet.
Porting to Python 3.4
=====================
This section lists previously described changes and other bugfixes
that may require changes to your code.
* The ABCs defined in :mod:`importlib.abc` now either raise the appropriate
exception or return a default value instead of raising
:exc:`NotImplementedError` blindly. This will only affect code calling
:func:`super` and falling through all the way to the ABCs. For compatibility,
catch both :exc:`NotImplementedError` or the appropriate exception as needed.
|
