blob: da1762053821b498b86953e0b47e62e15e0967a9 [file] [log] [blame]
Benjamin Petersonf10a79a2008-10-11 00:49:57 +00001****************************
2 What's New in Python 2.7
3****************************
4
5:Author: A.M. Kuchling (amk at amk.ca)
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 in a parenthetical comment.
42
43 XXX Describe the transmogrify() function added to the socket
44 module.
45 (Contributed by P.Y. Developer; :issue:`12345`.)
46
47 This saves the maintainer some effort going through the SVN logs
48 when researching a change.
49
50This article explains the new features in Python 2.7.
51No release schedule has been decided yet for 2.7.
52
53.. Compare with previous release in 2 - 3 sentences here.
54 add hyperlink when the documentation becomes available online.
55
56.. ========================================================================
57.. Large, PEP-level features and changes should be described here.
58.. Should there be a new section here for 3k migration?
59.. Or perhaps a more general section describing module changes/deprecation?
60.. ========================================================================
61
62
63
64Other Language Changes
65======================
66
67Some smaller changes made to the core Python language are:
68
Mark Dickinson54bc1ec2008-12-17 16:19:07 +000069* The :func:`int` and :func:`long` types gained a ``bit_length``
70 method that returns the number of bits necessary to represent
71 its argument in binary::
72
73 >>> n = 37
74 >>> bin(37)
75 '0b100101'
76 >>> n.bit_length()
77 6
78 >>> n = 2**123-1
79 >>> n.bit_length()
80 123
81 >>> (n+1).bit_length()
82 124
83
84 (Contributed by Fredrik Johansson and Victor Stinner; :issue:`3439`.)
85
Benjamin Petersonf10a79a2008-10-11 00:49:57 +000086
87.. ======================================================================
88
89
90Optimizations
91-------------
92
93To be written.
94
95.. ======================================================================
96
97New, Improved, and Deprecated Modules
98=====================================
99
100As in every release, Python's standard library received a number of
101enhancements and bug fixes. Here's a partial list of the most notable
102changes, sorted alphabetically by module name. Consult the
103:file:`Misc/NEWS` file in the source tree for a more complete list of
104changes, or look through the Subversion logs for all the details.
105
Georg Brandl1f01deb2009-01-03 22:47:39 +0000106* A new function in the :mod:`subprocess` module,
107 :func:`check_output`, runs a command with a specified set of arguments
108 and returns the command's output as a string if the command runs without
109 error, or raises a :exc:`CalledProcessError` exception otherwise.
110
111 ::
112
113 >>> subprocess.check_output(['df', '-h', '.'])
114 'Filesystem Size Used Avail Capacity Mounted on\n
115 /dev/disk0s2 52G 49G 3.0G 94% /\n'
116
117 >>> subprocess.check_output(['df', '-h', '/bogus'])
118 ...
119 subprocess.CalledProcessError: Command '['df', '-h', '/bogus']' returned non-zero exit status 1
120
121 (Contributed by Gregory P. Smith.)
122
Benjamin Petersonf10a79a2008-10-11 00:49:57 +0000123
124.. ======================================================================
125.. whole new modules get described in subsections here
126
127.. ======================================================================
128
129
130Build and C API Changes
131=======================
132
133Changes to Python's build process and to the C API include:
134
Georg Brandl1f01deb2009-01-03 22:47:39 +0000135* If you use the :file:`.gdbinit` file provided with Python,
136 the "pyo" macro in the 2.7 version will now work when the thread being
137 debugged doesn't hold the GIL; the macro will now acquire it before printing.
138 (Contributed by haypo XXX; :issue:`3632`.)
Benjamin Petersonf10a79a2008-10-11 00:49:57 +0000139
140.. ======================================================================
141
142Port-Specific Changes: Windows
143-----------------------------------
144
Georg Brandl1f01deb2009-01-03 22:47:39 +0000145* The :mod:`msvcrt` module now contains some constants from
146 the :file:`crtassem.h` header file:
147 :data:`CRT_ASSEMBLY_VERSION`,
148 :data:`VC_ASSEMBLY_PUBLICKEYTOKEN`,
149 and :data:`LIBRARIES_ASSEMBLY_NAME_PREFIX`.
150 (Added by Martin von Loewis (XXX check); :issue:`4365`.)
Benjamin Petersonf10a79a2008-10-11 00:49:57 +0000151
152.. ======================================================================
153
154Port-Specific Changes: Mac OS X
155-----------------------------------
156
157
158.. ======================================================================
159
160Porting to Python 2.7
161=====================
162
163This section lists previously described changes and other bugfixes
164that may require changes to your code:
165
166To be written.
167
168.. ======================================================================
169
170
171.. _acks27:
172
173Acknowledgements
174================
175
176The author would like to thank the following people for offering
177suggestions, corrections and assistance with various drafts of this
178article: no one yet.
179