blob: 1a7d08016d26fe9fbac62fc2eb5d997ce97d5d52 [file] [log] [blame]
Raymond Hettinger6e6565b2009-06-28 20:56:11 +00001****************************
Raymond Hettingerf558ddd2009-06-28 21:37:08 +00002 What's New In Python 3.2
Raymond Hettinger6e6565b2009-06-28 20:56:11 +00003****************************
4
5:Author: Raymond Hettinger
6:Release: |release|
7:Date: |today|
8
9.. $Id$
10 Rules for maintenance:
11
12 * Anyone can add text to this document. Do not spend very much time
13 on the wording of your changes, because your text will probably
14 get rewritten to some degree.
15
16 * The maintainer will go through Misc/NEWS periodically and add
17 changes; it's therefore more important to add your changes to
18 Misc/NEWS than to this file.
19
20 * This is not a complete list of every single change; completeness
21 is the purpose of Misc/NEWS. Some changes I consider too small
22 or esoteric to include. If such a change is added to the text,
23 I'll just remove it. (This is another reason you shouldn't spend
24 too much time on writing your addition.)
25
26 * If you want to draw your new text to the attention of the
27 maintainer, add 'XXX' to the beginning of the paragraph or
28 section.
29
30 * It's OK to just add a fragmentary note about a change. For
31 example: "XXX Describe the transmogrify() function added to the
32 socket module." The maintainer will research the change and
33 write the necessary text.
34
35 * You can comment out your additions if you like, but it's not
36 necessary (especially when a final release is some months away).
37
38 * Credit the author of a patch or bugfix. Just the name is
39 sufficient; the e-mail address isn't necessary.
40
41 * It's helpful to add the bug/patch number as a comment:
42
43 % Patch 12345
44 XXX Describe the transmogrify() function added to the socket
45 module.
46 (Contributed by P.Y. Developer.)
47
48 This saves the maintainer the effort of going through the SVN log
49 when researching a change.
50
51This article explains the new features in Python 3.2, compared to 3.1.
52
53
54PEP XXX: Stub
55=============
56
57
58Other Language Changes
59======================
60
61Some smaller changes made to the core Python language are:
62
63* Stub
64
65
66New, Improved, and Deprecated Modules
67=====================================
68
Raymond Hettingerf558ddd2009-06-28 21:37:08 +000069* The previously deprecated :func:`string.maketrans` function has been
70 removed in favor of the static methods, :meth:`bytes.maketrans` and
71 :meth:`bytearray.maketrans`. This change solves the confusion around which
72 types were supported by the :mod:`string` module. Now, :class:`str`,
73 :class:`bytes`, and :class:`bytearray` each have their own **maketrans** and
74 **translate** methods with intermediate translation tables of the
75 appropriate type.
Raymond Hettinger6e6565b2009-06-28 20:56:11 +000076
Raymond Hettingerf558ddd2009-06-28 21:37:08 +000077 (Contributed by Georg Brandl; :issue:`5675`.)
78
79* The previously deprecated :func:`contextlib.nested` function has been
80 removed in favor of a plain :keyword:`with` statement which can
81 accept multiple context managers. The latter technique is faster
82 (because it is built-in), and it does a better job finalizing multiple
83 context managers when one of them raises an exception.
84
85 (Contributed by Georg Brandl and Mattias Brändström;
86 `appspot issue 53094 <http://codereview.appspot.com/53094>`_.)
Raymond Hettinger6e6565b2009-06-28 20:56:11 +000087
Tarek Ziadé7aa6da02010-04-20 09:13:23 +000088* The :func:`shutil.copytree` function has two new options
89
90 * ignore_dangling_symlinks: when symlinks=false (meaning that the function
91 copy the file pointed by the symlink, not the symlink itself)
92 this option will silent the error thrown if the file doesn't exists.
93
94 * copy_function: a callable that will be used to copy files.
95 :func:`shutil.copy2` is used by default.
96
97 (Contributed by Tarek Ziade)
98
Antoine Pitroud42bc512009-11-10 23:18:31 +000099Multi-threading
100===============
101
102* The mechanism for serializing execution of concurrently running Python
103 threads (generally known as the GIL or Global Interpreter Lock) has been
104 rewritten. Among the objectives were more predictable switching intervals
105 and reduced overhead due to lock contention and the number of ensuing
106 system calls. The notion of a "check interval" to allow thread switches
107 has been abandoned and replaced by an absolute duration expressed in
108 seconds. This parameter is tunable through :func:`sys.setswitchinterval()`.
109 It currently defaults to 5 milliseconds.
110
111 Additional details about the implementation can be read from a `python-dev
112 mailing-list message
113 <http://mail.python.org/pipermail/python-dev/2009-October/093321.html>`_
114 (however, "priority requests" as exposed in this message have not been
115 kept for inclusion).
116
117 (Contributed by Antoine Pitrou)
118
Antoine Pitrou5bab5082009-11-13 22:58:45 +0000119* Recursive locks (created with the :func:`threading.RLock` API) now benefit
120 from a C implementation which makes them as fast as regular locks, and
121 between 10x and 15x faster than their previous pure Python implementation.
122
123 (Contributed by Antoine Pitrou; :issue:`3001`.)
124
Antoine Pitroud42bc512009-11-10 23:18:31 +0000125
Raymond Hettinger6e6565b2009-06-28 20:56:11 +0000126Optimizations
127=============
128
129Major performance enhancements have been added:
130
131* Stub
132
133IDLE
134====
135
136* Stub
137
138
139Build and C API Changes
140=======================
141
142Changes to Python's build process and to the C API include:
143
144* Stub
145
146
Raymond Hettingerf558ddd2009-06-28 21:37:08 +0000147Porting to Python 3.2
Raymond Hettinger6e6565b2009-06-28 20:56:11 +0000148=====================
149
150This section lists previously described changes and other bugfixes
151that may require changes to your code:
152
153* Stub