Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1 | **************************** |
| 2 | What's New In Python 3.3 |
| 3 | **************************** |
| 4 | |
| 5 | :Author: Raymond Hettinger |
| 6 | :Release: |release| |
| 7 | :Date: |today| |
| 8 | |
Éric Araujo | b07b97f | 2011-10-05 01:03:34 +0200 | [diff] [blame] | 9 | .. Rules for maintenance: |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 10 | |
| 11 | * Anyone can add text to this document. Do not spend very much time |
| 12 | on the wording of your changes, because your text will probably |
| 13 | get rewritten to some degree. |
| 14 | |
| 15 | * The maintainer will go through Misc/NEWS periodically and add |
| 16 | changes; it's therefore more important to add your changes to |
| 17 | Misc/NEWS than to this file. |
| 18 | |
| 19 | * This is not a complete list of every single change; completeness |
| 20 | is the purpose of Misc/NEWS. Some changes I consider too small |
| 21 | or esoteric to include. If such a change is added to the text, |
| 22 | I'll just remove it. (This is another reason you shouldn't spend |
| 23 | too much time on writing your addition.) |
| 24 | |
| 25 | * If you want to draw your new text to the attention of the |
| 26 | maintainer, add 'XXX' to the beginning of the paragraph or |
| 27 | section. |
| 28 | |
| 29 | * It's OK to just add a fragmentary note about a change. For |
| 30 | example: "XXX Describe the transmogrify() function added to the |
| 31 | socket module." The maintainer will research the change and |
| 32 | write the necessary text. |
| 33 | |
| 34 | * You can comment out your additions if you like, but it's not |
| 35 | necessary (especially when a final release is some months away). |
| 36 | |
| 37 | * Credit the author of a patch or bugfix. Just the name is |
| 38 | sufficient; the e-mail address isn't necessary. |
| 39 | |
| 40 | * It's helpful to add the bug/patch number as a comment: |
| 41 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 42 | XXX Describe the transmogrify() function added to the socket |
| 43 | module. |
Éric Araujo | b07b97f | 2011-10-05 01:03:34 +0200 | [diff] [blame] | 44 | (Contributed by P.Y. Developer in :issue:`12345`.) |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 45 | |
Éric Araujo | b07b97f | 2011-10-05 01:03:34 +0200 | [diff] [blame] | 46 | This saves the maintainer the effort of going through the Mercurial log |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 47 | when researching a change. |
| 48 | |
| 49 | This article explains the new features in Python 3.3, compared to 3.2. |
| 50 | |
Georg Brandl | 988049a | 2012-06-24 18:12:24 +0200 | [diff] [blame] | 51 | .. note:: Beta users should be aware that this document is currently in |
Nick Coghlan | b47b539 | 2012-05-26 01:31:25 +1000 | [diff] [blame] | 52 | draft form. It will be updated substantially as Python 3.3 moves towards |
| 53 | release, so it's worth checking back even after reading earlier versions. |
| 54 | |
| 55 | |
Éric Araujo | 859aad6 | 2012-06-24 00:07:41 -0400 | [diff] [blame] | 56 | PEP 405: Virtual Environments |
| 57 | ============================= |
Nick Coghlan | b47b539 | 2012-05-26 01:31:25 +1000 | [diff] [blame] | 58 | |
Éric Araujo | 859aad6 | 2012-06-24 00:07:41 -0400 | [diff] [blame] | 59 | - inspired by ``virtualenv``, a tool widely used by the community |
| 60 | - change to the interpreter to avoid hacks |
Nick Coghlan | b47b539 | 2012-05-26 01:31:25 +1000 | [diff] [blame] | 61 | |
Éric Araujo | 859aad6 | 2012-06-24 00:07:41 -0400 | [diff] [blame] | 62 | The :mod:`venv` module and ``pyvenv`` script (inspired by ``virtualenv``, a |
| 63 | tool widely used by the community). |
| 64 | |
| 65 | .. also mention the interpreter changes that avoid the hacks used in virtualenv |
Nick Coghlan | b47b539 | 2012-05-26 01:31:25 +1000 | [diff] [blame] | 66 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 67 | |
Éric Araujo | 859aad6 | 2012-06-24 00:07:41 -0400 | [diff] [blame] | 68 | PEP 420: Namespace Packages |
| 69 | =========================== |
| 70 | |
| 71 | Native support for package directories that don't require ``__init__.py`` |
| 72 | marker files and can automatically span multiple path segments (inspired by |
| 73 | various third party approaches to namespace packages, as described in |
| 74 | :pep:`420`) |
| 75 | |
| 76 | |
| 77 | .. _pep-3118-update: |
Nick Coghlan | 98e2070 | 2012-03-06 21:50:13 +1000 | [diff] [blame] | 78 | |
Stefan Krah | 9a2d99e | 2012-02-25 12:24:21 +0100 | [diff] [blame] | 79 | PEP 3118: New memoryview implementation and buffer protocol documentation |
| 80 | ========================================================================= |
| 81 | |
| 82 | :issue:`10181` - memoryview bug fixes and features. |
| 83 | Written by Stefan Krah. |
| 84 | |
| 85 | The new memoryview implementation comprehensively fixes all ownership and |
| 86 | lifetime issues of dynamically allocated fields in the Py_buffer struct |
| 87 | that led to multiple crash reports. Additionally, several functions that |
| 88 | crashed or returned incorrect results for non-contiguous or multi-dimensional |
| 89 | input have been fixed. |
| 90 | |
| 91 | The memoryview object now has a PEP-3118 compliant getbufferproc() |
| 92 | that checks the consumer's request type. Many new features have been |
| 93 | added, most of them work in full generality for non-contiguous arrays |
| 94 | and arrays with suboffsets. |
| 95 | |
| 96 | The documentation has been updated, clearly spelling out responsibilities |
| 97 | for both exporters and consumers. Buffer request flags are grouped into |
| 98 | basic and compound flags. The memory layout of non-contiguous and |
| 99 | multi-dimensional NumPy-style arrays is explained. |
| 100 | |
| 101 | Features |
| 102 | -------- |
| 103 | |
| 104 | * All native single character format specifiers in struct module syntax |
| 105 | (optionally prefixed with '@') are now supported. |
| 106 | |
| 107 | * With some restrictions, the cast() method allows changing of format and |
| 108 | shape of C-contiguous arrays. |
| 109 | |
| 110 | * Multi-dimensional list representations are supported for any array type. |
| 111 | |
| 112 | * Multi-dimensional comparisons are supported for any array type. |
| 113 | |
| 114 | * All array types are hashable if the exporting object is hashable |
Nick Coghlan | 98e2070 | 2012-03-06 21:50:13 +1000 | [diff] [blame] | 115 | and the view is read-only. (Contributed by Antoine Pitrou in |
| 116 | :issue:`13411`) |
| 117 | |
Stefan Krah | 9a2d99e | 2012-02-25 12:24:21 +0100 | [diff] [blame] | 118 | |
| 119 | * Arbitrary slicing of any 1-D arrays type is supported. For example, it |
| 120 | is now possible to reverse a memoryview in O(1) by using a negative step. |
| 121 | |
| 122 | API changes |
| 123 | ----------- |
| 124 | |
| 125 | * The maximum number of dimensions is officially limited to 64. |
| 126 | |
| 127 | * The representation of empty shape, strides and suboffsets is now |
| 128 | an empty tuple instead of None. |
| 129 | |
| 130 | * Accessing a memoryview element with format 'B' (unsigned bytes) |
| 131 | now returns an integer (in accordance with the struct module syntax). |
| 132 | For returning a bytes object the view must be cast to 'c' first. |
| 133 | |
Stefan Krah | 54c3203 | 2012-02-29 17:47:21 +0100 | [diff] [blame] | 134 | * For further changes see `Build and C API Changes`_ and `Porting C code`_ . |
Stefan Krah | 9a2d99e | 2012-02-25 12:24:21 +0100 | [diff] [blame] | 135 | |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 136 | .. _pep-393: |
| 137 | |
Ezio Melotti | 48a2f8f | 2011-09-29 00:18:19 +0300 | [diff] [blame] | 138 | PEP 393: Flexible String Representation |
| 139 | ======================================= |
| 140 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 141 | The Unicode string type is changed to support multiple internal |
| 142 | representations, depending on the character with the largest Unicode ordinal |
| 143 | (1, 2, or 4 bytes) in the represented string. This allows a space-efficient |
| 144 | representation in common cases, but gives access to full UCS-4 on all |
| 145 | systems. For compatibility with existing APIs, several representations may |
| 146 | exist in parallel; over time, this compatibility should be phased out. |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 147 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 148 | On the Python side, there should be no downside to this change. |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 149 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 150 | On the C API side, PEP 393 is fully backward compatible. The legacy API |
| 151 | should remain available at least five years. Applications using the legacy |
| 152 | API will not fully benefit of the memory reduction, or - worse - may use |
| 153 | a bit more memory, because Python may have to maintain two versions of each |
| 154 | string (in the legacy format and in the new efficient storage). |
| 155 | |
Antoine Pitrou | 0599b5b | 2011-11-29 22:45:07 +0100 | [diff] [blame] | 156 | Functionality |
| 157 | ------------- |
| 158 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 159 | Changes introduced by :pep:`393` are the following: |
Ezio Melotti | 48a2f8f | 2011-09-29 00:18:19 +0300 | [diff] [blame] | 160 | |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 161 | * Python now always supports the full range of Unicode codepoints, including |
| 162 | non-BMP ones (i.e. from ``U+0000`` to ``U+10FFFF``). The distinction between |
| 163 | narrow and wide builds no longer exists and Python now behaves like a wide |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 164 | build, even under Windows. |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 165 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 166 | * With the death of narrow builds, the problems specific to narrow builds have |
| 167 | also been fixed, for example: |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 168 | |
| 169 | * :func:`len` now always returns 1 for non-BMP characters, |
| 170 | so ``len('\U0010FFFF') == 1``; |
| 171 | |
| 172 | * surrogate pairs are not recombined in string literals, |
| 173 | so ``'\uDBFF\uDFFF' != '\U0010FFFF'``; |
| 174 | |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 175 | * indexing or slicing non-BMP characters returns the expected value, |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 176 | so ``'\U0010FFFF'[0]`` now returns ``'\U0010FFFF'`` and not ``'\uDBFF'``; |
| 177 | |
Antoine Pitrou | d136aec | 2011-11-17 01:48:06 +0100 | [diff] [blame] | 178 | * all other functions in the standard library now correctly handle |
Antoine Pitrou | fd9b416 | 2011-10-24 00:14:43 +0200 | [diff] [blame] | 179 | non-BMP codepoints. |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 180 | |
Ezio Melotti | 48a2f8f | 2011-09-29 00:18:19 +0300 | [diff] [blame] | 181 | * The value of :data:`sys.maxunicode` is now always ``1114111`` (``0x10FFFF`` |
| 182 | in hexadecimal). The :c:func:`PyUnicode_GetMax` function still returns |
| 183 | either ``0xFFFF`` or ``0x10FFFF`` for backward compatibility, and it should |
| 184 | not be used with the new Unicode API (see :issue:`13054`). |
| 185 | |
Ezio Melotti | 397546a | 2011-09-29 08:34:36 +0300 | [diff] [blame] | 186 | * The :file:`./configure` flag ``--with-wide-unicode`` has been removed. |
Victor Stinner | 7d637ab | 2011-09-29 02:56:16 +0200 | [diff] [blame] | 187 | |
Antoine Pitrou | 0599b5b | 2011-11-29 22:45:07 +0100 | [diff] [blame] | 188 | Performance and resource usage |
| 189 | ------------------------------ |
| 190 | |
| 191 | The storage of Unicode strings now depends on the highest codepoint in the string: |
| 192 | |
| 193 | * pure ASCII and Latin1 strings (``U+0000-U+00FF``) use 1 byte per codepoint; |
| 194 | |
| 195 | * BMP strings (``U+0000-U+FFFF``) use 2 bytes per codepoint; |
| 196 | |
| 197 | * non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per codepoint. |
| 198 | |
Martin v. Löwis | de157cc | 2012-03-06 08:42:17 +0100 | [diff] [blame] | 199 | The net effect is that for most applications, memory usage of string |
| 200 | storage should decrease significantly - especially compared to former |
| 201 | wide unicode builds - as, in many cases, strings will be pure ASCII |
| 202 | even in international contexts (because many strings store non-human |
| 203 | language data, such as XML fragments, HTTP headers, JSON-encoded data, |
| 204 | etc.). We also hope that it will, for the same reasons, increase CPU |
| 205 | cache efficiency on non-trivial applications. The memory usage of |
| 206 | Python 3.3 is two to three times smaller than Python 3.2, and a little |
| 207 | bit better than Python 2.7, on a Django benchmark (see the PEP for |
| 208 | details). |
Antoine Pitrou | 0599b5b | 2011-11-29 22:45:07 +0100 | [diff] [blame] | 209 | |
Éric Araujo | b07b97f | 2011-10-05 01:03:34 +0200 | [diff] [blame] | 210 | |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 211 | PEP 3151: Reworking the OS and IO exception hierarchy |
| 212 | ===================================================== |
| 213 | |
| 214 | :pep:`3151` - Reworking the OS and IO exception hierarchy |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 215 | PEP written and implemented by Antoine Pitrou. |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 216 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 217 | The hierarchy of exceptions raised by operating system errors is now both |
| 218 | simplified and finer-grained. |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 219 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 220 | You don't have to worry anymore about choosing the appropriate exception |
| 221 | type between :exc:`OSError`, :exc:`IOError`, :exc:`EnvironmentError`, |
| 222 | :exc:`WindowsError`, :exc:`mmap.error`, :exc:`socket.error` or |
| 223 | :exc:`select.error`. All these exception types are now only one: |
| 224 | :exc:`OSError`. The other names are kept as aliases for compatibility |
| 225 | reasons. |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 226 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 227 | Also, it is now easier to catch a specific error condition. Instead of |
| 228 | inspecting the ``errno`` attribute (or ``args[0]``) for a particular |
| 229 | constant from the :mod:`errno` module, you can catch the adequate |
| 230 | :exc:`OSError` subclass. The available subclasses are the following: |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 231 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 232 | * :exc:`BlockingIOError` |
| 233 | * :exc:`ChildProcessError` |
| 234 | * :exc:`ConnectionError` |
| 235 | * :exc:`FileExistsError` |
| 236 | * :exc:`FileNotFoundError` |
| 237 | * :exc:`InterruptedError` |
| 238 | * :exc:`IsADirectoryError` |
| 239 | * :exc:`NotADirectoryError` |
| 240 | * :exc:`PermissionError` |
| 241 | * :exc:`ProcessLookupError` |
| 242 | * :exc:`TimeoutError` |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 243 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 244 | And the :exc:`ConnectionError` itself has finer-grained subclasses: |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 245 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 246 | * :exc:`BrokenPipeError` |
| 247 | * :exc:`ConnectionAbortedError` |
| 248 | * :exc:`ConnectionRefusedError` |
| 249 | * :exc:`ConnectionResetError` |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 250 | |
| 251 | Thanks to the new exceptions, common usages of the :mod:`errno` can now be |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 252 | avoided. For example, the following code written for Python 3.2:: |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 253 | |
| 254 | from errno import ENOENT, EACCES, EPERM |
| 255 | |
| 256 | try: |
| 257 | with open("document.txt") as f: |
| 258 | content = f.read() |
| 259 | except IOError as err: |
| 260 | if err.errno == ENOENT: |
| 261 | print("document.txt file is missing") |
| 262 | elif err.errno in (EACCES, EPERM): |
| 263 | print("You are not allowed to read document.txt") |
| 264 | else: |
| 265 | raise |
| 266 | |
Antoine Pitrou | 01fd26c | 2011-10-24 00:07:02 +0200 | [diff] [blame] | 267 | can now be written without the :mod:`errno` import and without manual |
| 268 | inspection of exception attributes:: |
Victor Stinner | a1bf298 | 2011-10-12 20:35:02 +0200 | [diff] [blame] | 269 | |
| 270 | try: |
| 271 | with open("document.txt") as f: |
| 272 | content = f.read() |
| 273 | except FileNotFoundError: |
| 274 | print("document.txt file is missing") |
| 275 | except PermissionError: |
| 276 | print("You are not allowed to read document.txt") |
| 277 | |
| 278 | |
Nick Coghlan | 1f7ce62 | 2012-01-13 21:43:40 +1000 | [diff] [blame] | 279 | PEP 380: Syntax for Delegating to a Subgenerator |
| 280 | ================================================ |
| 281 | |
Nick Coghlan | ab7bf21 | 2012-02-26 17:49:52 +1000 | [diff] [blame] | 282 | :pep:`380` - Syntax for Delegating to a Subgenerator |
| 283 | PEP written by Greg Ewing. |
| 284 | |
Nick Coghlan | 1f7ce62 | 2012-01-13 21:43:40 +1000 | [diff] [blame] | 285 | PEP 380 adds the ``yield from`` expression, allowing a generator to delegate |
| 286 | part of its operations to another generator. This allows a section of code |
| 287 | containing 'yield' to be factored out and placed in another generator. |
| 288 | Additionally, the subgenerator is allowed to return with a value, and the |
| 289 | value is made available to the delegating generator. |
Nick Coghlan | b9b281b | 2012-03-06 22:31:12 +1000 | [diff] [blame] | 290 | |
Nick Coghlan | 1f7ce62 | 2012-01-13 21:43:40 +1000 | [diff] [blame] | 291 | While designed primarily for use in delegating to a subgenerator, the ``yield |
| 292 | from`` expression actually allows delegation to arbitrary subiterators. |
| 293 | |
Nick Coghlan | b9b281b | 2012-03-06 22:31:12 +1000 | [diff] [blame] | 294 | For simple iterators, ``yield from iterable`` is essentially just a shortened |
| 295 | form of ``for item in iterable: yield item``:: |
| 296 | |
| 297 | >>> def g(x): |
| 298 | ... yield from range(x, 0, -1) |
| 299 | ... yield from range(x) |
| 300 | ... |
| 301 | >>> list(g(5)) |
| 302 | [5, 4, 3, 2, 1, 0, 1, 2, 3, 4] |
| 303 | |
| 304 | However, unlike an ordinary loop, ``yield from`` allows subgenerators to |
| 305 | receive sent and thrown values directly from the calling scope, and |
| 306 | return a final value to the outer generator:: |
| 307 | |
| 308 | >>> def accumulate(start=0): |
| 309 | ... tally = start |
| 310 | ... while 1: |
| 311 | ... next = yield |
| 312 | ... if next is None: |
| 313 | ... return tally |
| 314 | ... tally += next |
| 315 | ... |
| 316 | >>> def gather_tallies(tallies, start=0): |
| 317 | ... while 1: |
| 318 | ... tally = yield from accumulate() |
| 319 | ... tallies.append(tally) |
| 320 | ... |
| 321 | >>> tallies = [] |
| 322 | >>> acc = gather_tallies(tallies) |
| 323 | >>> next(acc) # Ensure the accumulator is ready to accept values |
| 324 | >>> for i in range(10): |
| 325 | ... acc.send(i) |
| 326 | ... |
| 327 | >>> acc.send(None) # Finish the first tally |
| 328 | >>> for i in range(5): |
| 329 | ... acc.send(i) |
| 330 | ... |
| 331 | >>> acc.send(None) # Finish the second tally |
| 332 | >>> tallies |
| 333 | [45, 10] |
| 334 | |
| 335 | The main principle driving this change is to allow even generators that are |
| 336 | designed to be used with the ``send`` and ``throw`` methods to be split into |
| 337 | multiple subgenerators as easily as a single large function can be split into |
| 338 | multiple subfunctions. |
| 339 | |
Nick Coghlan | 1f7ce62 | 2012-01-13 21:43:40 +1000 | [diff] [blame] | 340 | (Implementation by Greg Ewing, integrated into 3.3 by Renaud Blanch, Ryan |
| 341 | Kelly and Nick Coghlan, documentation by Zbigniew Jędrzejewski-Szmek and |
| 342 | Nick Coghlan) |
| 343 | |
| 344 | |
Nick Coghlan | ab7bf21 | 2012-02-26 17:49:52 +1000 | [diff] [blame] | 345 | PEP 409: Suppressing exception context |
| 346 | ====================================== |
| 347 | |
| 348 | :pep:`409` - Suppressing exception context |
| 349 | PEP written by Ethan Furman, implemented by Ethan Furman and Nick Coghlan. |
| 350 | |
| 351 | PEP 409 introduces new syntax that allows the display of the chained |
| 352 | exception context to be disabled. This allows cleaner error messages in |
| 353 | applications that convert between exception types:: |
| 354 | |
| 355 | >>> class D: |
| 356 | ... def __init__(self, extra): |
| 357 | ... self._extra_attributes = extra |
| 358 | ... def __getattr__(self, attr): |
| 359 | ... try: |
| 360 | ... return self._extra_attributes[attr] |
| 361 | ... except KeyError: |
| 362 | ... raise AttributeError(attr) from None |
| 363 | ... |
| 364 | >>> D({}).x |
| 365 | Traceback (most recent call last): |
| 366 | File "<stdin>", line 1, in <module> |
| 367 | File "<stdin>", line 8, in __getattr__ |
| 368 | AttributeError: x |
| 369 | |
| 370 | Without the ``from None`` suffix to suppress the cause, the original |
| 371 | exception would be displayed by default:: |
| 372 | |
| 373 | >>> class C: |
| 374 | ... def __init__(self, extra): |
| 375 | ... self._extra_attributes = extra |
| 376 | ... def __getattr__(self, attr): |
| 377 | ... try: |
| 378 | ... return self._extra_attributes[attr] |
| 379 | ... except KeyError: |
| 380 | ... raise AttributeError(attr) |
| 381 | ... |
| 382 | >>> C({}).x |
| 383 | Traceback (most recent call last): |
| 384 | File "<stdin>", line 6, in __getattr__ |
| 385 | KeyError: 'x' |
| 386 | |
| 387 | During handling of the above exception, another exception occurred: |
| 388 | |
| 389 | Traceback (most recent call last): |
| 390 | File "<stdin>", line 1, in <module> |
| 391 | File "<stdin>", line 8, in __getattr__ |
| 392 | AttributeError: x |
| 393 | |
| 394 | No debugging capability is lost, as the original exception context remains |
| 395 | available if needed (for example, if an intervening library has incorrectly |
| 396 | suppressed valuable underlying details):: |
| 397 | |
| 398 | >>> try: |
| 399 | ... D({}).x |
| 400 | ... except AttributeError as exc: |
| 401 | ... print(repr(exc.__context__)) |
| 402 | ... |
| 403 | KeyError('x',) |
| 404 | |
| 405 | |
Nick Coghlan | 98e2070 | 2012-03-06 21:50:13 +1000 | [diff] [blame] | 406 | PEP 414: Explicit Unicode literals |
| 407 | ====================================== |
| 408 | |
| 409 | :pep:`414` - Explicit Unicode literals |
| 410 | PEP written by Armin Ronacher. |
| 411 | |
| 412 | To ease the transition from Python 2 for Unicode aware Python applications |
| 413 | that make heavy use of Unicode literals, Python 3.3 once again supports the |
| 414 | "``u``" prefix for string literals. This prefix has no semantic significance |
| 415 | in Python 3, it is provided solely to reduce the number of purely mechanical |
| 416 | changes in migrating to Python 3, making it easier for developers to focus on |
| 417 | the more significant semantic changes (such as the stricter default |
| 418 | separation of binary and text data). |
| 419 | |
| 420 | |
Antoine Pitrou | 6bbd76b | 2011-11-25 19:10:05 +0100 | [diff] [blame] | 421 | PEP 3155: Qualified name for classes and functions |
| 422 | ================================================== |
| 423 | |
| 424 | :pep:`3155` - Qualified name for classes and functions |
| 425 | PEP written and implemented by Antoine Pitrou. |
| 426 | |
| 427 | Functions and class objects have a new ``__qualname__`` attribute representing |
| 428 | the "path" from the module top-level to their definition. For global functions |
| 429 | and classes, this is the same as ``__name__``. For other functions and classes, |
| 430 | it provides better information about where they were actually defined, and |
| 431 | how they might be accessible from the global scope. |
| 432 | |
| 433 | Example with (non-bound) methods:: |
Nick Coghlan | 2dfe6b0 | 2012-01-14 14:19:49 +1000 | [diff] [blame] | 434 | |
Antoine Pitrou | 6bbd76b | 2011-11-25 19:10:05 +0100 | [diff] [blame] | 435 | >>> class C: |
| 436 | ... def meth(self): |
| 437 | ... pass |
| 438 | >>> C.meth.__name__ |
| 439 | 'meth' |
| 440 | >>> C.meth.__qualname__ |
| 441 | 'C.meth' |
| 442 | |
| 443 | Example with nested classes:: |
| 444 | |
| 445 | >>> class C: |
| 446 | ... class D: |
| 447 | ... def meth(self): |
| 448 | ... pass |
| 449 | ... |
| 450 | >>> C.D.__name__ |
| 451 | 'D' |
| 452 | >>> C.D.__qualname__ |
| 453 | 'C.D' |
| 454 | >>> C.D.meth.__name__ |
| 455 | 'meth' |
| 456 | >>> C.D.meth.__qualname__ |
| 457 | 'C.D.meth' |
| 458 | |
| 459 | Example with nested functions:: |
| 460 | |
| 461 | >>> def outer(): |
| 462 | ... def inner(): |
| 463 | ... pass |
| 464 | ... return inner |
| 465 | ... |
| 466 | >>> outer().__name__ |
| 467 | 'inner' |
| 468 | >>> outer().__qualname__ |
| 469 | 'outer.<locals>.inner' |
| 470 | |
Antoine Pitrou | e7ede06 | 2011-11-25 19:11:26 +0100 | [diff] [blame] | 471 | The string representation of those objects is also changed to include the |
Antoine Pitrou | 6bbd76b | 2011-11-25 19:10:05 +0100 | [diff] [blame] | 472 | new, more precise information:: |
| 473 | |
| 474 | >>> str(C.D) |
| 475 | "<class '__main__.C.D'>" |
| 476 | >>> str(C.D.meth) |
| 477 | '<function C.D.meth at 0x7f46b9fe31e0>' |
| 478 | |
| 479 | |
Antoine Pitrou | d94adb7 | 2012-07-07 17:33:42 +0200 | [diff] [blame] | 480 | PEP 412: Key-Sharing Dictionary |
| 481 | =============================== |
| 482 | |
| 483 | :pep:`412` - Key-Sharing Dictionary |
| 484 | PEP written and implemented by Mark Shannon. |
| 485 | |
| 486 | Dictionaries used for the storage of objects' attributes are now able to |
| 487 | share part of their internal storage between each other (namely, the part |
| 488 | which stores the keys and their respective hashes). This reduces the memory |
| 489 | consumption of programs creating many instances of non-builtin types. |
| 490 | |
| 491 | |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 492 | Using importlib as the Implementation of Import |
| 493 | =============================================== |
| 494 | :issue:`2377` - Replace __import__ w/ importlib.__import__ |
| 495 | :issue:`13959` - Re-implement parts of :mod:`imp` in pure Python |
| 496 | :issue:`14605` - Make import machinery explicit |
| 497 | :issue:`14646` - Require loaders set __loader__ and __package__ |
| 498 | |
| 499 | (Written by Brett Cannon) |
| 500 | |
| 501 | The :func:`__import__` function is now powered by :func:`importlib.__import__`. |
| 502 | This work leads to the completion of "phase 2" of :pep:`302`. There are |
| 503 | multiple benefits to this change. First, it has allowed for more of the |
| 504 | machinery powering import to be exposed instead of being implicit and hidden |
| 505 | within the C code. It also provides a single implementation for all Python VMs |
| 506 | supporting Python 3.3 to use, helping to end any VM-specific deviations in |
| 507 | import semantics. And finally it eases the maintenance of import, allowing for |
| 508 | future growth to occur. |
| 509 | |
| 510 | For the common user, this change should result in no visible change in |
| 511 | semantics. Any possible changes required in one's code to handle this change |
| 512 | should read the `Porting Python code`_ section of this document to see what |
| 513 | needs to be changed, but it will only affect those that currently manipulate |
| 514 | import or try calling it programmatically. |
| 515 | |
| 516 | New APIs |
| 517 | -------- |
| 518 | One of the large benefits of this work is the exposure of what goes into |
| 519 | making the import statement work. That means the various importers that were |
| 520 | once implicit are now fully exposed as part of the :mod:`importlib` package. |
| 521 | |
Brett Cannon | 077ef45 | 2012-08-02 17:50:06 -0400 | [diff] [blame^] | 522 | The abstract base classes defined in :mod:`importlib.abc` have been expanded |
| 523 | to properly delineate between :term:`meta path finders <meta path finder>` |
| 524 | and :term:`path entry finders <path entry finder>` by introducing |
| 525 | :class:`importlib.abc.MetaPathFinder` and |
| 526 | :class:`importlib.abc.PathEntryFinder`, respectively. The old ABC of |
| 527 | :class:`importlib.abc.Finder` is now only provided for backwards-compatibility |
| 528 | and does not enforce any method requirements. |
| 529 | |
| 530 | In terms of finders, :class:`importlib.machinery.FileFinder` exposes the |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 531 | mechanism used to search for source and bytecode files of a module. Previously |
| 532 | this class was an implicit member of :attr:`sys.path_hooks`. |
| 533 | |
| 534 | For loaders, the new abstract base class :class:`importlib.abc.FileLoader` helps |
| 535 | write a loader that uses the file system as the storage mechanism for a module's |
| 536 | code. The loader for source files |
| 537 | (:class:`importlib.machinery.SourceFileLoader`), sourceless bytecode files |
| 538 | (:class:`importlib.machinery.SourcelessFileLoader`), and extension modules |
| 539 | (:class:`importlib.machinery.ExtensionFileLoader`) are now available for |
| 540 | direct use. |
| 541 | |
| 542 | :exc:`ImportError` now has ``name`` and ``path`` attributes which are set when |
| 543 | there is relevant data to provide. The message for failed imports will also |
| 544 | provide the full name of the module now instead of just the tail end of the |
| 545 | module's name. |
| 546 | |
| 547 | The :func:`importlib.invalidate_caches` function will now call the method with |
| 548 | the same name on all finders cached in :attr:`sys.path_importer_cache` to help |
| 549 | clean up any stored state as necessary. |
| 550 | |
| 551 | Visible Changes |
| 552 | --------------- |
| 553 | [For potential required changes to code, see the `Porting Python code`_ |
| 554 | section] |
| 555 | |
| 556 | Beyond the expanse of what :mod:`importlib` now exposes, there are other |
| 557 | visible changes to import. The biggest is that :attr:`sys.meta_path` and |
Brett Cannon | 077ef45 | 2012-08-02 17:50:06 -0400 | [diff] [blame^] | 558 | :attr:`sys.path_hooks` now store all of the meta path finders and path entry |
| 559 | hooks used by import. Previously the finders were implicit and hidden within |
| 560 | the C code of import instead of being directly exposed. This means that one can |
| 561 | now easily remove or change the order of the various finders to fit one's needs. |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 562 | |
| 563 | Another change is that all modules have a ``__loader__`` attribute, storing the |
| 564 | loader used to create the module. :pep:`302` has been updated to make this |
| 565 | attribute mandatory for loaders to implement, so in the future once 3rd-party |
| 566 | loaders have been updated people will be able to rely on the existence of the |
| 567 | attribute. Until such time, though, import is setting the module post-load. |
| 568 | |
| 569 | Loaders are also now expected to set the ``__package__`` attribute from |
| 570 | :pep:`366`. Once again, import itself is already setting this on all loaders |
| 571 | from :mod:`importlib` and import itself is setting the attribute post-load. |
| 572 | |
| 573 | ``None`` is now inserted into :attr:`sys.path_importer_cache` when no finder |
| 574 | can be found on :attr:`sys.path_hooks`. Since :class:`imp.NullImporter` is not |
| 575 | directly exposed on :attr:`sys.path_hooks` it could no longer be relied upon to |
| 576 | always be available to use as a value representing no finder found. |
| 577 | |
| 578 | All other changes relate to semantic changes which should be taken into |
| 579 | consideration when updating code for Python 3.3, and thus should be read about |
| 580 | in the `Porting Python code`_ section of this document. |
| 581 | |
| 582 | |
R David Murray | 0fa2edd | 2012-05-25 17:59:56 -0400 | [diff] [blame] | 583 | New Email Package Features |
| 584 | ========================== |
| 585 | |
R David Murray | cb448cf | 2012-05-25 22:25:56 -0400 | [diff] [blame] | 586 | Policy Framework |
| 587 | ---------------- |
| 588 | |
R David Murray | 0fa2edd | 2012-05-25 17:59:56 -0400 | [diff] [blame] | 589 | The email package now has a :mod:`~email.policy` framework. A |
| 590 | :class:`~email.policy.Policy` is an object with several methods and properties |
| 591 | that control how the email package behaves. The primary policy for Python 3.3 |
| 592 | is the :class:`~email.policy.Compat32` policy, which provides backward |
| 593 | compatibility with the email package in Python 3.2. A ``policy`` can be |
| 594 | specified when an email message is parsed by a :mod:`~email.parser`, or when a |
| 595 | :class:`~email.message.Message` object is created, or when an email is |
| 596 | serialized using a :mod:`~email.generator`. Unless overridden, a policy passed |
| 597 | to a ``parser`` is inherited by all the ``Message`` object and sub-objects |
| 598 | created by the ``parser``. By default a ``generator`` will use the policy of |
| 599 | the ``Message`` object it is serializing. The default policy is |
| 600 | :data:`~email.policy.compat32`. |
| 601 | |
| 602 | The minimum set of controls implemented by all ``policy`` objects are: |
| 603 | |
| 604 | =============== ======================================================= |
| 605 | max_line_length The maximum length, excluding the linesep character(s), |
| 606 | individual lines may have when a ``Message`` is |
| 607 | serialized. Defaults to 78. |
| 608 | |
| 609 | linesep The character used to separate individual lines when a |
| 610 | ``Message`` is serialized. Defaults to ``\n``. |
| 611 | |
| 612 | cte_type ``7bit`` or ``8bit``. ``8bit`` applies only to a |
| 613 | ``Bytes`` ``generator``, and means that non-ASCII may |
| 614 | be used where allowed by the protocol (or where it |
| 615 | exists in the original input). |
| 616 | |
| 617 | raise_on_defect Causes a ``parser`` to raise error when defects are |
| 618 | encountered instead of adding them to the ``Message`` |
| 619 | object's ``defects`` list. |
| 620 | =============== ======================================================= |
| 621 | |
| 622 | A new policy instance, with new settings, is created using the |
| 623 | :meth:`~email.policy.Policy.clone` method of policy objects. ``clone`` takes |
| 624 | any of the above controls as keyword arguments. Any control not specified in |
| 625 | the call retains its default value. Thus you can create a policy that uses |
| 626 | ``\r\n`` linesep characters like this:: |
| 627 | |
Georg Brandl | 3539afd | 2012-05-30 22:03:20 +0200 | [diff] [blame] | 628 | mypolicy = compat32.clone(linesep='\r\n') |
R David Murray | 0fa2edd | 2012-05-25 17:59:56 -0400 | [diff] [blame] | 629 | |
| 630 | Policies can be used to make the generation of messages in the format needed by |
| 631 | your application simpler. Instead of having to remember to specify |
| 632 | ``linesep='\r\n'`` in all the places you call a ``generator``, you can specify |
| 633 | it once, when you set the policy used by the ``parser`` or the ``Message``, |
| 634 | whichever your program uses to create ``Message`` objects. On the other hand, |
| 635 | if you need to generate messages in multiple forms, you can still specify the |
| 636 | parameters in the appropriate ``generator`` call. Or you can have custom |
| 637 | policy instances for your different cases, and pass those in when you create |
| 638 | the ``generator``. |
| 639 | |
| 640 | |
R David Murray | cb448cf | 2012-05-25 22:25:56 -0400 | [diff] [blame] | 641 | Provisional Policy with New Header API |
| 642 | -------------------------------------- |
| 643 | |
| 644 | While the policy framework is worthwhile all by itself, the main motivation for |
| 645 | introducing it is to allow the creation of new policies that implement new |
| 646 | features for the email package in a way that maintains backward compatibility |
| 647 | for those who do not use the new policies. Because the new policies introduce a |
| 648 | new API, we are releasing them in Python 3.3 as a :term:`provisional policy |
| 649 | <provisional package>`. Backwards incompatible changes (up to and including |
| 650 | removal of the code) may occur if deemed necessary by the core developers. |
| 651 | |
| 652 | The new policies are instances of :class:`~email.policy.EmailPolicy`, |
| 653 | and add the following additional controls: |
| 654 | |
| 655 | =============== ======================================================= |
| 656 | refold_source Controls whether or not headers parsed by a |
| 657 | :mod:`~email.parser` are refolded by the |
| 658 | :mod:`~email.generator`. It can be ``none``, ``long``, |
| 659 | or ``all``. The default is ``long``, which means that |
| 660 | source headers with a line longer than |
| 661 | ``max_line_length`` get refolded. ``none`` means no |
| 662 | line get refolded, and ``all`` means that all lines |
| 663 | get refolded. |
| 664 | |
| 665 | header_factory A callable that take a ``name`` and ``value`` and |
| 666 | produces a custom header object. |
| 667 | =============== ======================================================= |
| 668 | |
| 669 | The ``header_factory`` is the key to the new features provided by the new |
| 670 | policies. When one of the new policies is used, any header retrieved from |
| 671 | a ``Message`` object is an object produced by the ``header_factory``, and any |
| 672 | time you set a header on a ``Message`` it becomes an object produced by |
| 673 | ``header_factory``. All such header objects have a ``name`` attribute equal |
| 674 | to the header name. Address and Date headers have additional attributes |
| 675 | that give you access to the parsed data of the header. This means you can now |
| 676 | do things like this:: |
| 677 | |
| 678 | >>> m = Message(policy=SMTP) |
| 679 | >>> m['To'] = 'Éric <foo@example.com>' |
| 680 | >>> m['to'] |
| 681 | 'Éric <foo@example.com>' |
| 682 | >>> m['to'].addresses |
| 683 | (Address(display_name='Éric', username='foo', domain='example.com'),) |
| 684 | >>> m['to'].addresses[0].username |
| 685 | 'foo' |
| 686 | >>> m['to'].addresses[0].display_name |
| 687 | 'Éric' |
| 688 | >>> m['Date'] = email.utils.localtime() |
| 689 | >>> m['Date'].datetime |
| 690 | datetime.datetime(2012, 5, 25, 21, 39, 24, 465484, tzinfo=datetime.timezone(datetime.timedelta(-1, 72000), 'EDT')) |
| 691 | >>> m['Date'] |
| 692 | 'Fri, 25 May 2012 21:44:27 -0400' |
| 693 | >>> print(m) |
| 694 | To: =?utf-8?q?=C3=89ric?= <foo@example.com> |
| 695 | Date: Fri, 25 May 2012 21:44:27 -0400 |
| 696 | |
| 697 | You will note that the unicode display name is automatically encoded as |
| 698 | ``utf-8`` when the message is serialized, but that when the header is accessed |
| 699 | directly, you get the unicode version. This eliminates any need to deal with |
| 700 | the :mod:`email.header` :meth:`~email.header.decode_header` or |
| 701 | :meth:`~email.header.make_header` functions. |
| 702 | |
| 703 | You can also create addresses from parts:: |
| 704 | |
| 705 | >>> m['cc'] = [Group('pals', [Address('Bob', 'bob', 'example.com'), |
| 706 | ... Address('Sally', 'sally', 'example.com')]), |
| 707 | ... Address('Bonzo', addr_spec='bonz@laugh.com')] |
| 708 | >>> print(m) |
| 709 | To: =?utf-8?q?=C3=89ric?= <foo@example.com> |
| 710 | Date: Fri, 25 May 2012 21:44:27 -0400 |
| 711 | cc: pals: Bob <bob@example.com>, Sally <sally@example.com>;, Bonzo <bonz@laugh.com> |
| 712 | |
| 713 | Decoding to unicode is done automatically:: |
| 714 | |
| 715 | >>> m2 = message_from_string(str(m)) |
| 716 | >>> m2['to'] |
| 717 | 'Éric <foo@example.com>' |
| 718 | |
| 719 | When you parse a message, you can use the ``addresses`` and ``groups`` |
| 720 | attributes of the header objects to access the groups and individual |
| 721 | addresses:: |
| 722 | |
| 723 | >>> m2['cc'].addresses |
| 724 | (Address(display_name='Bob', username='bob', domain='example.com'), Address(display_name='Sally', username='sally', domain='example.com'), Address(display_name='Bonzo', username='bonz', domain='laugh.com')) |
| 725 | >>> m2['cc'].groups |
| 726 | (Group(display_name='pals', addresses=(Address(display_name='Bob', username='bob', domain='example.com'), Address(display_name='Sally', username='sally', domain='example.com')), Group(display_name=None, addresses=(Address(display_name='Bonzo', username='bonz', domain='laugh.com'),)) |
| 727 | |
| 728 | In summary, if you use one of the new policies, header manipulation works the |
| 729 | way it ought to: your application works with unicode strings, and the email |
| 730 | package transparently encodes and decodes the unicode to and from the RFC |
| 731 | standard Content Transfer Encodings. |
| 732 | |
| 733 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 734 | Other Language Changes |
| 735 | ====================== |
| 736 | |
| 737 | Some smaller changes made to the core Python language are: |
| 738 | |
Antoine Pitrou | 7b578b3 | 2011-11-29 22:47:11 +0100 | [diff] [blame] | 739 | * Added support for Unicode name aliases and named sequences. |
| 740 | Both :func:`unicodedata.lookup()` and ``'\N{...}'`` now resolve name aliases, |
| 741 | and :func:`unicodedata.lookup()` resolves named sequences too. |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 742 | |
Antoine Pitrou | 7b578b3 | 2011-11-29 22:47:11 +0100 | [diff] [blame] | 743 | (Contributed by Ezio Melotti in :issue:`12753`) |
Ezio Melotti | 931b8aa | 2011-10-21 21:57:36 +0300 | [diff] [blame] | 744 | |
Antoine Pitrou | 7b578b3 | 2011-11-29 22:47:11 +0100 | [diff] [blame] | 745 | * Equality comparisons on :func:`range` objects now return a result reflecting |
| 746 | the equality of the underlying sequences generated by those range objects. |
Ezio Melotti | 931b8aa | 2011-10-21 21:57:36 +0300 | [diff] [blame] | 747 | |
Sandro Tosi | cd89912 | 2012-01-22 12:16:04 +0100 | [diff] [blame] | 748 | (:issue:`13201`) |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 749 | |
Antoine Pitrou | 7b578b3 | 2011-11-29 22:47:11 +0100 | [diff] [blame] | 750 | * The ``count()``, ``find()``, ``rfind()``, ``index()`` and ``rindex()`` |
| 751 | methods of :class:`bytes` and :class:`bytearray` objects now accept an |
| 752 | integer between 0 and 255 as their first argument. |
Mark Dickinson | 3664568 | 2011-10-23 19:53:01 +0100 | [diff] [blame] | 753 | |
Petri Lehtinen | 6c3f1dd | 2012-06-26 10:23:07 +0300 | [diff] [blame] | 754 | (Contributed by Petri Lehtinen in :issue:`12170`) |
Mark Dickinson | 3664568 | 2011-10-23 19:53:01 +0100 | [diff] [blame] | 755 | |
Eli Bendersky | 7add4ea | 2012-03-17 15:14:35 +0200 | [diff] [blame] | 756 | * New methods have been added to :class:`list` and :class:`bytearray`: |
| 757 | ``copy()`` and ``clear()``. |
| 758 | |
| 759 | (:issue:`10516`) |
Petri Lehtinen | 61ea8a0 | 2011-11-24 22:00:46 +0200 | [diff] [blame] | 760 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 761 | * Raw bytes literals can now be written ``rb"..."`` as well as ``br"..."``. |
| 762 | (Contributed by Antoine Pitrou in :issue:`13748`.) |
| 763 | |
| 764 | * :meth:`dict.setdefault` now does only one lookup for the given key, making |
| 765 | it atomic when used with built-in types. |
| 766 | (Contributed by Filip Gruszczyński in :issue:`13521`.) |
| 767 | |
| 768 | |
Benjamin Peterson | e50d6ab | 2012-04-03 00:52:18 -0400 | [diff] [blame] | 769 | .. XXX mention new error messages for passing wrong number of arguments to functions |
| 770 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 771 | |
Antoine Pitrou | 79341e7 | 2012-05-17 21:13:45 +0200 | [diff] [blame] | 772 | A Finer-Grained Import Lock |
| 773 | =========================== |
| 774 | |
| 775 | Previous versions of CPython have always relied on a global import lock. |
| 776 | This led to unexpected annoyances, such as deadlocks when importing a module |
| 777 | would trigger code execution in a different thread as a side-effect. |
| 778 | Clumsy workarounds were sometimes employed, such as the |
| 779 | :c:func:`PyImport_ImportModuleNoBlock` C API function. |
| 780 | |
| 781 | In Python 3.3, importing a module takes a per-module lock. This correctly |
| 782 | serializes importation of a given module from multiple threads (preventing |
| 783 | the exposure of incompletely initialized modules), while eliminating the |
| 784 | aforementioned annoyances. |
| 785 | |
| 786 | (contributed by Antoine Pitrou in :issue:`9260`.) |
| 787 | |
| 788 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 789 | New and Improved Modules |
| 790 | ======================== |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 791 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 792 | abc |
| 793 | --- |
| 794 | |
| 795 | Improved support for abstract base classes containing descriptors composed with |
| 796 | abstract methods. The recommended approach to declaring abstract descriptors is |
| 797 | now to provide :attr:`__isabstractmethod__` as a dynamically updated |
| 798 | property. The built-in descriptors have been updated accordingly. |
| 799 | |
| 800 | * :class:`abc.abstractproperty` has been deprecated, use :class:`property` |
| 801 | with :func:`abc.abstractmethod` instead. |
| 802 | * :class:`abc.abstractclassmethod` has been deprecated, use |
| 803 | :class:`classmethod` with :func:`abc.abstractmethod` instead. |
| 804 | * :class:`abc.abstractstaticmethod` has been deprecated, use |
| 805 | :class:`staticmethod` with :func:`abc.abstractmethod` instead. |
| 806 | |
| 807 | (Contributed by Darren Dale in :issue:`11610`) |
| 808 | |
Meador Inge | c5dbb3d | 2011-09-20 21:48:16 -0500 | [diff] [blame] | 809 | array |
| 810 | ----- |
| 811 | |
| 812 | The :mod:`array` module supports the :c:type:`long long` type using ``q`` and |
| 813 | ``Q`` type codes. |
| 814 | |
| 815 | (Contributed by Oren Tirosh and Hirokazu Yamamoto in :issue:`1172711`) |
| 816 | |
| 817 | |
Nadeem Vawda | d7e5c6e | 2012-02-12 01:34:18 +0200 | [diff] [blame] | 818 | bz2 |
| 819 | --- |
| 820 | |
| 821 | The :mod:`bz2` module has been rewritten from scratch. In the process, several |
| 822 | new features have been added: |
| 823 | |
| 824 | * :class:`bz2.BZ2File` can now read from and write to arbitrary file-like |
| 825 | objects, by means of its constructor's *fileobj* argument. |
| 826 | |
| 827 | (Contributed by Nadeem Vawda in :issue:`5863`) |
| 828 | |
| 829 | * :class:`bz2.BZ2File` and :func:`bz2.decompress` can now decompress |
| 830 | multi-stream inputs (such as those produced by the :program:`pbzip2` tool). |
| 831 | :class:`bz2.BZ2File` can now also be used to create this type of file, using |
| 832 | the ``'a'`` (append) mode. |
| 833 | |
| 834 | (Contributed by Nir Aides in :issue:`1625`) |
| 835 | |
| 836 | * :class:`bz2.BZ2File` now implements all of the :class:`io.BufferedIOBase` API, |
| 837 | except for the :meth:`detach` and :meth:`truncate` methods. |
| 838 | |
| 839 | |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 840 | codecs |
| 841 | ------ |
| 842 | |
Antoine Pitrou | 4f86343 | 2012-02-12 02:12:47 +0100 | [diff] [blame] | 843 | The :mod:`~encodings.mbcs` codec has been rewritten to handle correctly |
Georg Brandl | ff962c5 | 2012-02-04 08:55:56 +0100 | [diff] [blame] | 844 | ``replace`` and ``ignore`` error handlers on all Windows versions. The |
| 845 | :mod:`~encodings.mbcs` codec now supports all error handlers, instead of only |
| 846 | ``replace`` to encode and ``ignore`` to decode. |
Victor Stinner | 3a50e70 | 2011-10-18 21:21:00 +0200 | [diff] [blame] | 847 | |
Georg Brandl | ff962c5 | 2012-02-04 08:55:56 +0100 | [diff] [blame] | 848 | A new Windows-only codec has been added: ``cp65001`` (:issue:`13216`). It is the |
| 849 | Windows code page 65001 (Windows UTF-8, ``CP_UTF8``). For example, it is used |
| 850 | by ``sys.stdout`` if the console output code page is set to cp65001 (e.g., using |
| 851 | ``chcp 65001`` command). |
Victor Stinner | 2f3ca9f | 2011-10-27 01:38:56 +0200 | [diff] [blame] | 852 | |
Georg Brandl | ff962c5 | 2012-02-04 08:55:56 +0100 | [diff] [blame] | 853 | Multibyte CJK decoders now resynchronize faster. They only ignore the first |
Georg Brandl | 6c0929b | 2011-07-09 11:43:33 +0200 | [diff] [blame] | 854 | byte of an invalid byte sequence. For example, ``b'\xff\n'.decode('gb2312', |
| 855 | 'replace')`` now returns a ``\n`` after the replacement character. |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 856 | |
Georg Brandl | 6c0929b | 2011-07-09 11:43:33 +0200 | [diff] [blame] | 857 | (:issue:`12016`) |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 858 | |
Georg Brandl | ff962c5 | 2012-02-04 08:55:56 +0100 | [diff] [blame] | 859 | Incremental CJK codec encoders are no longer reset at each call to their |
| 860 | encode() methods. For example:: |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 861 | |
| 862 | $ ./python -q |
| 863 | >>> import codecs |
| 864 | >>> encoder = codecs.getincrementalencoder('hz')('strict') |
| 865 | >>> b''.join(encoder.encode(x) for x in '\u52ff\u65bd\u65bc\u4eba\u3002 Bye.') |
| 866 | b'~{NpJ)l6HK!#~} Bye.' |
| 867 | |
Georg Brandl | 6c0929b | 2011-07-09 11:43:33 +0200 | [diff] [blame] | 868 | This example gives ``b'~{Np~}~{J)~}~{l6~}~{HK~}~{!#~} Bye.'`` with older Python |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 869 | versions. |
| 870 | |
Georg Brandl | 6c0929b | 2011-07-09 11:43:33 +0200 | [diff] [blame] | 871 | (:issue:`12100`) |
Victor Stinner | 2cded9c | 2011-07-08 01:45:13 +0200 | [diff] [blame] | 872 | |
Victor Stinner | 9f4b1e9 | 2011-11-10 20:56:30 +0100 | [diff] [blame] | 873 | The ``unicode_internal`` codec has been deprecated. |
| 874 | |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 875 | |
| 876 | collections |
| 877 | ----------- |
| 878 | |
| 879 | Addition of a new :class:`~collections.ChainMap` class to allow treating a |
| 880 | number of mappings as a single unit. |
| 881 | |
| 882 | (Written by Raymond Hettinger for :issue:`11089`, made public in |
| 883 | :issue:`11297`) |
| 884 | |
| 885 | The abstract base classes have been moved in a new :mod:`collections.abc` |
| 886 | module, to better differentiate between the abstract and the concrete |
| 887 | collections classes. Aliases for ABCs are still present in the |
| 888 | :mod:`collections` module to preserve existing imports. |
| 889 | |
| 890 | (:issue:`11085`) |
| 891 | |
| 892 | .. XXX addition of __slots__ to ABCs not recorded here: internal detail |
| 893 | |
| 894 | |
Nick Coghlan | 3267a30 | 2012-05-21 22:54:43 +1000 | [diff] [blame] | 895 | contextlib |
| 896 | ---------- |
| 897 | |
| 898 | :class:`~collections.ExitStack` now provides a solid foundation for |
| 899 | programmatic manipulation of context managers and similar cleanup |
| 900 | functionality. Unlike the previous ``contextlib.nested`` API (which was |
| 901 | deprecated and removed), the new API is designed to work correctly |
| 902 | regardless of whether context managers acquire their resources in |
Nick Coghlan | 161ea6a | 2012-05-22 23:04:42 +1000 | [diff] [blame] | 903 | their ``__init__`` method (for example, file objects) or in their |
Nick Coghlan | 3267a30 | 2012-05-21 22:54:43 +1000 | [diff] [blame] | 904 | ``__enter__`` method (for example, synchronisation objects from the |
| 905 | :mod:`threading` module). |
| 906 | |
| 907 | (:issue:`13585`) |
| 908 | |
| 909 | |
Éric Araujo | 84b8ed8 | 2011-08-29 21:42:47 +0200 | [diff] [blame] | 910 | crypt |
| 911 | ----- |
| 912 | |
Victor Stinner | c78fb33 | 2011-09-21 03:35:44 +0200 | [diff] [blame] | 913 | Addition of salt and modular crypt format and the :func:`~crypt.mksalt` |
| 914 | function to the :mod:`crypt` module. |
Éric Araujo | 84b8ed8 | 2011-08-29 21:42:47 +0200 | [diff] [blame] | 915 | |
| 916 | (:issue:`10924`) |
| 917 | |
Victor Stinner | a7878b7 | 2011-07-14 23:07:44 +0200 | [diff] [blame] | 918 | curses |
| 919 | ------ |
| 920 | |
Victor Stinner | 0fdfceb | 2011-11-25 22:10:02 +0100 | [diff] [blame] | 921 | * If the :mod:`curses` module is linked to the ncursesw library, use Unicode |
| 922 | functions when Unicode strings or characters are passed (e.g. |
| 923 | :c:func:`waddwstr`), and bytes functions otherwise (e.g. :c:func:`waddstr`). |
| 924 | * Use the locale encoding instead of ``utf-8`` to encode Unicode strings. |
| 925 | * :class:`curses.window` has a new :attr:`curses.window.encoding` attribute. |
Victor Stinner | c78fb33 | 2011-09-21 03:35:44 +0200 | [diff] [blame] | 926 | * The :class:`curses.window` class has a new :meth:`~curses.window.get_wch` |
| 927 | method to get a wide character |
| 928 | * The :mod:`curses` module has a new :meth:`~curses.unget_wch` function to |
| 929 | push a wide character so the next :meth:`~curses.window.get_wch` will return |
| 930 | it |
Victor Stinner | a7878b7 | 2011-07-14 23:07:44 +0200 | [diff] [blame] | 931 | |
Victor Stinner | c78fb33 | 2011-09-21 03:35:44 +0200 | [diff] [blame] | 932 | (Contributed by Iñigo Serna in :issue:`6755`) |
Victor Stinner | a7878b7 | 2011-07-14 23:07:44 +0200 | [diff] [blame] | 933 | |
Stefan Krah | 1919b7e | 2012-03-21 18:25:23 +0100 | [diff] [blame] | 934 | decimal |
| 935 | ------- |
| 936 | |
| 937 | :issue:`7652` - integrate fast native decimal arithmetic. |
| 938 | C-module and libmpdec written by Stefan Krah. |
| 939 | |
| 940 | The new C version of the decimal module integrates the high speed libmpdec |
Stefan Krah | bf80308 | 2012-04-01 13:07:24 +0200 | [diff] [blame] | 941 | library for arbitrary precision correctly-rounded decimal floating point |
| 942 | arithmetic. libmpdec conforms to IBM's General Decimal Arithmetic Specification. |
Stefan Krah | 1919b7e | 2012-03-21 18:25:23 +0100 | [diff] [blame] | 943 | |
Stefan Krah | 0c0914e | 2012-04-09 20:31:15 +0200 | [diff] [blame] | 944 | Performance gains range from 10x for database applications to 100x for |
Stefan Krah | bf80308 | 2012-04-01 13:07:24 +0200 | [diff] [blame] | 945 | numerically intensive applications. These numbers are expected gains |
| 946 | for standard precisions used in decimal floating point arithmetic. Since |
| 947 | the precision is user configurable, the exact figures may vary. For example, |
| 948 | in integer bignum arithmetic the differences can be significantly higher. |
| 949 | |
| 950 | The following table is meant as an illustration. Benchmarks are available |
Georg Brandl | 204e789 | 2012-04-01 13:10:58 +0200 | [diff] [blame] | 951 | at http://www.bytereef.org/mpdecimal/quickstart.html. |
Stefan Krah | 1919b7e | 2012-03-21 18:25:23 +0100 | [diff] [blame] | 952 | |
| 953 | +---------+-------------+--------------+-------------+ |
| 954 | | | decimal.py | _decimal | speedup | |
| 955 | +=========+=============+==============+=============+ |
Stefan Krah | 0c0914e | 2012-04-09 20:31:15 +0200 | [diff] [blame] | 956 | | pi | 38.89s | 0.38s | 100x | |
Stefan Krah | 1919b7e | 2012-03-21 18:25:23 +0100 | [diff] [blame] | 957 | +---------+-------------+--------------+-------------+ |
| 958 | | telco | 172.19s | 5.68s | 30x | |
| 959 | +---------+-------------+--------------+-------------+ |
| 960 | | psycopg | 3.57s | 0.29s | 12x | |
| 961 | +---------+-------------+--------------+-------------+ |
| 962 | |
| 963 | Features |
| 964 | ~~~~~~~~ |
| 965 | |
| 966 | * The :exc:`~decimal.FloatOperation` signal optionally enables stricter |
| 967 | semantics for mixing floats and Decimals. |
| 968 | |
| 969 | * If Python is compiled without threads, the C version automatically |
| 970 | disables the expensive thread local context machinery. In this case, |
| 971 | the variable :data:`~decimal.HAVE_THREADS` is set to False. |
| 972 | |
| 973 | API changes |
| 974 | ~~~~~~~~~~~ |
| 975 | |
| 976 | * The C module has the following context limits, depending on the machine |
| 977 | architecture: |
| 978 | |
| 979 | +-------------------+---------------------+------------------------------+ |
| 980 | | | 32-bit | 64-bit | |
| 981 | +===================+=====================+==============================+ |
| 982 | | :const:`MAX_PREC` | :const:`425000000` | :const:`999999999999999999` | |
| 983 | +-------------------+---------------------+------------------------------+ |
| 984 | | :const:`MAX_EMAX` | :const:`425000000` | :const:`999999999999999999` | |
| 985 | +-------------------+---------------------+------------------------------+ |
| 986 | | :const:`MIN_EMIN` | :const:`-425000000` | :const:`-999999999999999999` | |
| 987 | +-------------------+---------------------+------------------------------+ |
| 988 | |
| 989 | * In the context templates (:class:`~decimal.DefaultContext`, |
| 990 | :class:`~decimal.BasicContext` and :class:`~decimal.ExtendedContext`) |
| 991 | the magnitude of :attr:`~decimal.Context.Emax` and |
| 992 | :attr:`~decimal.Context.Emin` has changed to :const:`999999`. |
| 993 | |
| 994 | * The :class:`~decimal.Decimal` constructor in decimal.py does not observe |
| 995 | the context limits and converts values with arbitrary exponents or precision |
| 996 | exactly. Since the C version has internal limits, the following scheme is |
| 997 | used: If possible, values are converted exactly, otherwise |
| 998 | :exc:`~decimal.InvalidOperation` is raised and the result is NaN. In the |
| 999 | latter case it is always possible to use :meth:`~decimal.Context.create_decimal` |
| 1000 | in order to obtain a rounded or inexact value. |
| 1001 | |
| 1002 | |
| 1003 | * The power function in decimal.py is always correctly-rounded. In the |
| 1004 | C version, it is defined in terms of the correctly-rounded |
| 1005 | :meth:`~decimal.Decimal.exp` and :meth:`~decimal.Decimal.ln` functions, |
| 1006 | but the final result is only "almost always correctly rounded". |
| 1007 | |
| 1008 | |
| 1009 | * In the C version, the context dictionary containing the signals is a |
| 1010 | :class:`~collections.abc.MutableMapping`. For speed reasons, |
| 1011 | :attr:`~decimal.Context.flags` and :attr:`~decimal.Context.traps` always |
| 1012 | refer to the same :class:`~collections.abc.MutableMapping` that the context |
| 1013 | was initialized with. If a new signal dictionary is assigned, |
| 1014 | :attr:`~decimal.Context.flags` and :attr:`~decimal.Context.traps` |
| 1015 | are updated with the new values, but they do not reference the RHS |
| 1016 | dictionary. |
| 1017 | |
| 1018 | |
| 1019 | * Pickling a :class:`~decimal.Context` produces a different output in order |
| 1020 | to have a common interchange format for the Python and C versions. |
| 1021 | |
| 1022 | |
| 1023 | * The order of arguments in the :class:`~decimal.Context` constructor has been |
| 1024 | changed to match the order displayed by :func:`repr`. |
| 1025 | |
| 1026 | |
Victor Stinner | 024e37a | 2011-03-31 01:31:06 +0200 | [diff] [blame] | 1027 | faulthandler |
| 1028 | ------------ |
| 1029 | |
| 1030 | New module: :mod:`faulthandler`. |
| 1031 | |
| 1032 | * :envvar:`PYTHONFAULTHANDLER` |
| 1033 | * :option:`-X` ``faulthandler`` |
| 1034 | |
Victor Stinner | 811db3b | 2011-09-21 03:20:03 +0200 | [diff] [blame] | 1035 | ftplib |
| 1036 | ------ |
| 1037 | |
| 1038 | The :class:`~ftplib.FTP_TLS` class now provides a new |
| 1039 | :func:`~ftplib.FTP_TLS.ccc` function to revert control channel back to |
Florent Xicluna | 6d57d21 | 2011-10-23 22:23:57 +0200 | [diff] [blame] | 1040 | plaintext. This can be useful to take advantage of firewalls that know how to |
Victor Stinner | 811db3b | 2011-09-21 03:20:03 +0200 | [diff] [blame] | 1041 | handle NAT with non-secure FTP without opening fixed ports. |
| 1042 | |
| 1043 | (Contributed by Giampaolo Rodolà in :issue:`12139`) |
| 1044 | |
| 1045 | |
Christian Heimes | 3194037 | 2012-06-26 10:16:55 +0200 | [diff] [blame] | 1046 | hmac |
| 1047 | ---- |
| 1048 | |
| 1049 | A new :func:`~hmac.compare_digest` function has been added to prevent |
| 1050 | side channel attacks on digests through timing analysis. |
| 1051 | |
| 1052 | (Contributed by Nick Coghlan and Christian Heimes in issue:`15061`) |
| 1053 | |
| 1054 | |
Antoine Pitrou | 5a8bc6f | 2011-11-17 02:20:48 +0100 | [diff] [blame] | 1055 | imaplib |
| 1056 | ------- |
| 1057 | |
| 1058 | The :class:`~imaplib.IMAP4_SSL` constructor now accepts an SSLContext |
| 1059 | parameter to control parameters of the secure channel. |
| 1060 | |
| 1061 | (Contributed by Sijin Joseph in :issue:`8808`) |
| 1062 | |
| 1063 | |
Nick Coghlan | 2f92e54 | 2012-06-23 19:39:55 +1000 | [diff] [blame] | 1064 | inspect |
| 1065 | ------- |
| 1066 | |
| 1067 | A new :func:`~inspect.getclosurevars` function has been added. This function |
| 1068 | reports the current binding of all names referenced from the function body and |
| 1069 | where those names were resolved, making it easier to verify correct internal |
| 1070 | state when testing code that relies on stateful closures. |
| 1071 | |
| 1072 | (Contributed by Meador Inge and Nick Coghlan in :issue:`13062`) |
| 1073 | |
Nick Coghlan | 04e2e3f | 2012-06-23 19:52:05 +1000 | [diff] [blame] | 1074 | A new :func:`~inspect.getgeneratorlocals` function has been added. This |
| 1075 | function reports the current binding of local variables in the generator's |
| 1076 | stack frame, making it easier to verify correct internal state when testing |
| 1077 | generators. |
| 1078 | |
| 1079 | (Contributed by Meador Inge in :issue:`15153`) |
| 1080 | |
Charles-François Natali | dc3044c | 2012-01-09 22:40:02 +0100 | [diff] [blame] | 1081 | io |
| 1082 | -- |
| 1083 | |
Charles-François Natali | d612de1 | 2012-01-14 11:51:00 +0100 | [diff] [blame] | 1084 | The :func:`~io.open` function has a new ``'x'`` mode that can be used to |
| 1085 | exclusively create a new file, and raise a :exc:`FileExistsError` if the file |
| 1086 | already exists. It is based on the C11 'x' mode to fopen(). |
Charles-François Natali | dc3044c | 2012-01-09 22:40:02 +0100 | [diff] [blame] | 1087 | |
| 1088 | (Contributed by David Townshend in :issue:`12760`) |
| 1089 | |
| 1090 | |
Nick Coghlan | dc9b255 | 2012-05-20 21:01:57 +1000 | [diff] [blame] | 1091 | ipaddress |
| 1092 | --------- |
| 1093 | |
| 1094 | The new :mod:`ipaddress` module provides tools for creating and manipulating |
| 1095 | objects representing IPv4 and IPv6 addresses, networks and interfaces (i.e. |
| 1096 | an IP address associated with a specific IP subnet). |
| 1097 | |
| 1098 | (Contributed by Google and Peter Moody in :pep:`3144`) |
| 1099 | |
Nadeem Vawda | 3459922 | 2011-12-09 01:32:46 +0200 | [diff] [blame] | 1100 | lzma |
| 1101 | ---- |
| 1102 | |
| 1103 | The newly-added :mod:`lzma` module provides data compression and decompression |
| 1104 | using the LZMA algorithm, including support for the ``.xz`` and ``.lzma`` |
| 1105 | file formats. |
| 1106 | |
| 1107 | (Contributed by Nadeem Vawda and Per Øyvind Karlsen in :issue:`6715`) |
| 1108 | |
| 1109 | |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1110 | math |
| 1111 | ---- |
| 1112 | |
| 1113 | The :mod:`math` module has a new function: |
| 1114 | |
| 1115 | * :func:`~math.log2`: return the base-2 logarithm of *x* |
| 1116 | (Written by Mark Dickinson in :issue:`11888`). |
| 1117 | |
| 1118 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1119 | multiprocessing |
| 1120 | --------------- |
| 1121 | |
| 1122 | The new :func:`multiprocessing.connection.wait` function allows to poll |
| 1123 | multiple objects (such as connections, sockets and pipes) with a timeout. |
| 1124 | (Contributed by Richard Oudkerk in :issue:`12328`.) |
| 1125 | |
| 1126 | :class:`multiprocessing.Connection` objects can now be transferred over |
| 1127 | multiprocessing connections. |
| 1128 | (Contributed by Richard Oudkerk in :issue:`4892`.) |
| 1129 | |
| 1130 | |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1131 | nntplib |
| 1132 | ------- |
| 1133 | |
| 1134 | The :class:`nntplib.NNTP` class now supports the context manager protocol to |
| 1135 | unconditionally consume :exc:`socket.error` exceptions and to close the NNTP |
| 1136 | connection when done:: |
| 1137 | |
| 1138 | >>> from nntplib import NNTP |
Ezio Melotti | 3c14b4e | 2011-07-13 11:44:44 +0300 | [diff] [blame] | 1139 | >>> with NNTP('news.gmane.org') as n: |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1140 | ... n.group('gmane.comp.python.committers') |
| 1141 | ... |
Ezio Melotti | 04f648c | 2011-07-26 09:37:46 +0300 | [diff] [blame] | 1142 | ('211 1755 1 1755 gmane.comp.python.committers', 1755, 1, 1755, 'gmane.comp.python.committers') |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1143 | >>> |
| 1144 | |
| 1145 | (Contributed by Giampaolo Rodolà in :issue:`9795`) |
| 1146 | |
| 1147 | |
Giampaolo Rodolà | c9c2c8b | 2011-02-25 14:39:16 +0000 | [diff] [blame] | 1148 | os |
| 1149 | -- |
| 1150 | |
Charles-François Natali | a003af1 | 2011-06-01 20:30:52 +0200 | [diff] [blame] | 1151 | * The :mod:`os` module has a new :func:`~os.pipe2` function that makes it |
| 1152 | possible to create a pipe with :data:`~os.O_CLOEXEC` or |
| 1153 | :data:`~os.O_NONBLOCK` flags set atomically. This is especially useful to |
| 1154 | avoid race conditions in multi-threaded programs. |
| 1155 | |
Giampaolo Rodolà | 18e8bcb | 2011-02-25 20:57:54 +0000 | [diff] [blame] | 1156 | * The :mod:`os` module has a new :func:`~os.sendfile` function which provides |
| 1157 | an efficent "zero-copy" way for copying data from one file (or socket) |
| 1158 | descriptor to another. The phrase "zero-copy" refers to the fact that all of |
| 1159 | the copying of data between the two descriptors is done entirely by the |
| 1160 | kernel, with no copying of data into userspace buffers. :func:`~os.sendfile` |
| 1161 | can be used to efficiently copy data from a file on disk to a network socket, |
| 1162 | e.g. for downloading a file. |
Giampaolo Rodolà | c9c2c8b | 2011-02-25 14:39:16 +0000 | [diff] [blame] | 1163 | |
Giampaolo Rodolà | 18e8bcb | 2011-02-25 20:57:54 +0000 | [diff] [blame] | 1164 | (Patch submitted by Ross Lagerwall and Giampaolo Rodolà in :issue:`10882`.) |
| 1165 | |
| 1166 | * The :mod:`os` module has two new functions: :func:`~os.getpriority` and |
| 1167 | :func:`~os.setpriority`. They can be used to get or set process |
| 1168 | niceness/priority in a fashion similar to :func:`os.nice` but extended to all |
| 1169 | processes instead of just the current one. |
| 1170 | |
| 1171 | (Patch submitted by Giampaolo Rodolà in :issue:`10784`.) |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1172 | |
Charles-François Natali | 7372b06 | 2012-02-05 15:15:38 +0100 | [diff] [blame] | 1173 | * The :mod:`os` module has a new :func:`~os.fwalk` function similar to |
| 1174 | :func:`~os.walk` except that it also yields file descriptors referring to the |
| 1175 | directories visited. This is especially useful to avoid symlink races. |
| 1176 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1177 | * The new :func:`os.replace` function allows cross-platform renaming of a |
| 1178 | file with overwriting the destination. With :func:`os.rename`, an existing |
| 1179 | destination file is overwritten under POSIX, but raises an error under |
| 1180 | Windows. |
| 1181 | (Contributed by Antoine Pitrou in :issue:`8828`.) |
| 1182 | |
| 1183 | * The new :func:`os.get_terminal_size` function queries the size of the |
| 1184 | terminal attached to a file descriptor. |
| 1185 | (Contributed by Zbigniew Jędrzejewski-Szmek in :issue:`13609`.) |
| 1186 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1187 | .. XXX sort out this mess after beta1 |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1188 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1189 | * "at" functions (:issue:`4761`): |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1190 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1191 | * :func:`~os.faccessat` |
| 1192 | * :func:`~os.fchmodat` |
| 1193 | * :func:`~os.fchownat` |
| 1194 | * :func:`~os.fstatat` |
| 1195 | * :func:`~os.futimesat` |
| 1196 | * :func:`~os.linkat` |
| 1197 | * :func:`~os.mkdirat` |
| 1198 | * :func:`~os.mkfifoat` |
| 1199 | * :func:`~os.mknodat` |
| 1200 | * :func:`~os.openat` |
| 1201 | * :func:`~os.readlinkat` |
| 1202 | * :func:`~os.renameat` |
| 1203 | * :func:`~os.symlinkat` |
| 1204 | * :func:`~os.unlinkat` |
| 1205 | * :func:`~os.utimensat` |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1206 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1207 | * extended attributes (:issue:`12720`): |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1208 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1209 | * :func:`~os.fgetxattr` |
| 1210 | * :func:`~os.flistxattr` |
| 1211 | * :func:`~os.fremovexattr` |
| 1212 | * :func:`~os.fsetxattr` |
| 1213 | * :func:`~os.getxattr` |
| 1214 | * :func:`~os.lgetxattr` |
| 1215 | * :func:`~os.listxattr` |
| 1216 | * :func:`~os.llistxattr` |
| 1217 | * :func:`~os.lremovexattr` |
| 1218 | * :func:`~os.lsetxattr` |
| 1219 | * :func:`~os.removexattr` |
| 1220 | * :func:`~os.setxattr` |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1221 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1222 | * Scheduler functions (:issue:`12655`): |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1223 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1224 | * :func:`~os.sched_get_priority_max` |
| 1225 | * :func:`~os.sched_get_priority_min` |
| 1226 | * :func:`~os.sched_getaffinity` |
| 1227 | * :func:`~os.sched_getparam` |
| 1228 | * :func:`~os.sched_getscheduler` |
| 1229 | * :func:`~os.sched_rr_get_interval` |
| 1230 | * :func:`~os.sched_setaffinity` |
| 1231 | * :func:`~os.sched_setparam` |
| 1232 | * :func:`~os.sched_setscheduler` |
| 1233 | * :func:`~os.sched_yield` |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1234 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1235 | * Add some extra posix functions to the os module (:issue:`10812`): |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1236 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1237 | * :func:`~os.fexecve` |
| 1238 | * :func:`~os.futimens` |
| 1239 | * :func:`~os.futimes` |
| 1240 | * :func:`~os.lockf` |
| 1241 | * :func:`~os.lutimes` |
| 1242 | * :func:`~os.posix_fadvise` |
| 1243 | * :func:`~os.posix_fallocate` |
| 1244 | * :func:`~os.pread` |
| 1245 | * :func:`~os.pwrite` |
| 1246 | * :func:`~os.readv` |
| 1247 | * :func:`~os.sync` |
| 1248 | * :func:`~os.truncate` |
| 1249 | * :func:`~os.waitid` |
| 1250 | * :func:`~os.writev` |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1251 | |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1252 | * Other new functions: |
| 1253 | |
| 1254 | * :func:`~os.flistdir` (:issue:`10755`) |
| 1255 | * :func:`~os.getgrouplist` (:issue:`9344`) |
Victor Stinner | e506437 | 2011-10-14 00:08:29 +0200 | [diff] [blame] | 1256 | |
Giampaolo Rodolà | 424298a | 2011-03-03 18:34:06 +0000 | [diff] [blame] | 1257 | |
Georg Brandl | 4c7c3c5 | 2012-03-10 22:36:48 +0100 | [diff] [blame] | 1258 | pdb |
| 1259 | --- |
| 1260 | |
| 1261 | * Tab-completion is now available not only for command names, but also their |
| 1262 | arguments. For example, for the ``break`` command, function and file names |
| 1263 | are completed. (Contributed by Georg Brandl in :issue:`14210`) |
| 1264 | |
| 1265 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1266 | pickle |
| 1267 | ------ |
| 1268 | |
| 1269 | :class:`pickle.Pickler` objects now have an optional |
| 1270 | :attr:`~pickle.Pickler.dispatch_table` attribute allowing to set per-pickler |
| 1271 | reduction functions. |
| 1272 | (Contributed by Richard Oudkerk in :issue:`14166`.) |
| 1273 | |
| 1274 | |
Victor Stinner | 383c3fc | 2011-05-25 01:35:05 +0200 | [diff] [blame] | 1275 | pydoc |
| 1276 | ----- |
| 1277 | |
Victor Stinner | 6daa33c | 2011-05-25 01:41:22 +0200 | [diff] [blame] | 1278 | The Tk GUI and the :func:`~pydoc.serve` function have been removed from the |
| 1279 | :mod:`pydoc` module: ``pydoc -g`` and :func:`~pydoc.serve` have been deprecated |
| 1280 | in Python 3.2. |
Victor Stinner | 383c3fc | 2011-05-25 01:35:05 +0200 | [diff] [blame] | 1281 | |
| 1282 | |
Antoine Pitrou | ad09b5d | 2012-06-24 22:41:33 +0200 | [diff] [blame] | 1283 | re |
| 1284 | -- |
| 1285 | |
| 1286 | :class:`str` regular expressions now support ``\u`` and ``\U`` escapes. |
| 1287 | |
| 1288 | (Contributed by Serhiy Storchaka in :issue:`3665`.) |
| 1289 | |
| 1290 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1291 | sched |
| 1292 | ----- |
Victor Stinner | 754851f | 2011-04-19 23:58:51 +0200 | [diff] [blame] | 1293 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1294 | * :meth:`~sched.scheduler.run` now accepts a *blocking* parameter which when |
| 1295 | set to False makes the method execute the scheduled events due to expire |
| 1296 | soonest (if any) and then return immediately. |
| 1297 | This is useful in case you want to use the :class:`~sched.scheduler` in |
| 1298 | non-blocking applications. (Contributed by Giampaolo Rodolà in :issue:`13449`) |
Victor Stinner | 754851f | 2011-04-19 23:58:51 +0200 | [diff] [blame] | 1299 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1300 | * :class:`~sched.scheduler` class can now be safely used in multi-threaded |
| 1301 | environments. (Contributed by Josiah Carlson and Giampaolo Rodolà in |
| 1302 | :issue:`8684`) |
| 1303 | |
| 1304 | * *timefunc* and *delayfunct* parameters of :class:`~sched.scheduler` class |
| 1305 | constructor are now optional and defaults to :func:`time.time` and |
| 1306 | :func:`time.sleep` respectively. (Contributed by Chris Clark in |
| 1307 | :issue:`13245`) |
| 1308 | |
| 1309 | * :meth:`~sched.scheduler.enter` and :meth:`~sched.scheduler.enterabs` |
| 1310 | *argument* parameter is now optional. (Contributed by Chris Clark in |
| 1311 | :issue:`13245`) |
| 1312 | |
| 1313 | * :meth:`~sched.scheduler.enter` and :meth:`~sched.scheduler.enterabs` |
| 1314 | now accept a *kwargs* parameter. (Contributed by Chris Clark in |
| 1315 | :issue:`13245`) |
| 1316 | |
| 1317 | |
| 1318 | shutil |
| 1319 | ------ |
| 1320 | |
| 1321 | * The :mod:`shutil` module has these new fuctions: |
| 1322 | |
| 1323 | * :func:`~shutil.disk_usage`: provides total, used and free disk space |
| 1324 | statistics. (Contributed by Giampaolo Rodolà in :issue:`12442`) |
| 1325 | * :func:`~shutil.chown`: allows one to change user and/or group of the given |
| 1326 | path also specifying the user/group names and not only their numeric |
| 1327 | ids. (Contributed by Sandro Tosi in :issue:`12191`) |
Victor Stinner | a929335 | 2011-04-30 15:21:58 +0200 | [diff] [blame] | 1328 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1329 | * The new :func:`shutil.get_terminal_size` function returns the size of the |
| 1330 | terminal window the interpreter is attached to. |
| 1331 | (Contributed by Zbigniew Jędrzejewski-Szmek in :issue:`13609`.) |
| 1332 | |
| 1333 | * Several functions now take an optional ``symlinks`` argument: when that |
| 1334 | parameter is true, symlinks aren't dereferenced and the operation instead |
| 1335 | acts on the symlink itself (or creates one, if relevant). |
| 1336 | (Contributed by Hynek Schlawack in :issue:`12715`.) |
| 1337 | |
Nick Coghlan | 5b0eca1 | 2012-06-24 16:43:06 +1000 | [diff] [blame] | 1338 | * :func:`~shutil.rmtree` is now resistant to symlink attacks on platforms |
| 1339 | which support the new ``dir_fd`` parameter in :func:`os.open` and |
Georg Brandl | dba3b5c | 2012-06-26 09:36:14 +0200 | [diff] [blame] | 1340 | :func:`os.unlink`. (Contributed by Martin von Löwis and Hynek Schlawack |
Nick Coghlan | 5b0eca1 | 2012-06-24 16:43:06 +1000 | [diff] [blame] | 1341 | in :issue:`4489`.) |
| 1342 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1343 | |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1344 | |
Victor Stinner | a929335 | 2011-04-30 15:21:58 +0200 | [diff] [blame] | 1345 | signal |
| 1346 | ------ |
| 1347 | |
Victor Stinner | fa0e3d5 | 2011-05-09 01:01:09 +0200 | [diff] [blame] | 1348 | * The :mod:`signal` module has new functions: |
Victor Stinner | a929335 | 2011-04-30 15:21:58 +0200 | [diff] [blame] | 1349 | |
Victor Stinner | b3e7219 | 2011-05-08 01:46:11 +0200 | [diff] [blame] | 1350 | * :func:`~signal.pthread_sigmask`: fetch and/or change the signal mask of the |
| 1351 | calling thread (Contributed by Jean-Paul Calderone in :issue:`8407`) ; |
| 1352 | * :func:`~signal.pthread_kill`: send a signal to a thread ; |
| 1353 | * :func:`~signal.sigpending`: examine pending functions ; |
| 1354 | * :func:`~signal.sigwait`: wait a signal. |
Ross Lagerwall | bc80822 | 2011-06-25 12:13:40 +0200 | [diff] [blame] | 1355 | * :func:`~signal.sigwaitinfo`: wait for a signal, returning detailed |
| 1356 | information about it. |
| 1357 | * :func:`~signal.sigtimedwait`: like :func:`~signal.sigwaitinfo` but with a |
| 1358 | timeout. |
Victor Stinner | a929335 | 2011-04-30 15:21:58 +0200 | [diff] [blame] | 1359 | |
Victor Stinner | d49b1f1 | 2011-05-08 02:03:15 +0200 | [diff] [blame] | 1360 | * The signal handler writes the signal number as a single byte instead of |
| 1361 | a nul byte into the wakeup file descriptor. So it is possible to wait more |
| 1362 | than one signal and know which signals were raised. |
| 1363 | |
Victor Stinner | 388196e | 2011-05-10 17:13:00 +0200 | [diff] [blame] | 1364 | * :func:`signal.signal` and :func:`signal.siginterrupt` raise an OSError, |
| 1365 | instead of a RuntimeError: OSError has an errno attribute. |
| 1366 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1367 | smtplib |
| 1368 | ------- |
| 1369 | |
| 1370 | The :class:`~smtplib.SMTP_SSL` constructor and the :meth:`~smtplib.SMTP.starttls` |
| 1371 | method now accept an SSLContext parameter to control parameters of the secure |
| 1372 | channel. |
| 1373 | |
| 1374 | (Contributed by Kasun Herath in :issue:`8809`) |
| 1375 | |
| 1376 | |
Nick Coghlan | 96fe56a | 2011-08-22 11:55:57 +1000 | [diff] [blame] | 1377 | socket |
| 1378 | ------ |
| 1379 | |
Charles-François Natali | 47413c1 | 2011-10-06 19:47:44 +0200 | [diff] [blame] | 1380 | * The :class:`~socket.socket` class now exposes additional methods to process |
| 1381 | ancillary data when supported by the underlying platform: |
Nick Coghlan | 96fe56a | 2011-08-22 11:55:57 +1000 | [diff] [blame] | 1382 | |
Charles-François Natali | 47413c1 | 2011-10-06 19:47:44 +0200 | [diff] [blame] | 1383 | * :func:`~socket.socket.sendmsg` |
| 1384 | * :func:`~socket.socket.recvmsg` |
| 1385 | * :func:`~socket.socket.recvmsg_into` |
Nick Coghlan | 96fe56a | 2011-08-22 11:55:57 +1000 | [diff] [blame] | 1386 | |
Charles-François Natali | 47413c1 | 2011-10-06 19:47:44 +0200 | [diff] [blame] | 1387 | (Contributed by David Watson in :issue:`6560`, based on an earlier patch by |
| 1388 | Heiko Wundram) |
| 1389 | |
| 1390 | * The :class:`~socket.socket` class now supports the PF_CAN protocol family |
| 1391 | (http://en.wikipedia.org/wiki/Socketcan), on Linux |
| 1392 | (http://lwn.net/Articles/253425). |
| 1393 | |
| 1394 | (Contributed by Matthias Fuchs, updated by Tiago Gonçalves in :issue:`10141`) |
| 1395 | |
Charles-François Natali | 10b8cf4 | 2011-11-10 19:21:37 +0100 | [diff] [blame] | 1396 | * The :class:`~socket.socket` class now supports the PF_RDS protocol family |
| 1397 | (http://en.wikipedia.org/wiki/Reliable_Datagram_Sockets and |
| 1398 | http://oss.oracle.com/projects/rds/). |
Victor Stinner | 754851f | 2011-04-19 23:58:51 +0200 | [diff] [blame] | 1399 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1400 | |
Victor Stinner | 99c8b16 | 2011-05-24 12:05:19 +0200 | [diff] [blame] | 1401 | ssl |
| 1402 | --- |
| 1403 | |
Antoine Pitrou | 2c0a967 | 2011-11-17 02:09:13 +0100 | [diff] [blame] | 1404 | * The :mod:`ssl` module has two new random generation functions: |
Victor Stinner | 99c8b16 | 2011-05-24 12:05:19 +0200 | [diff] [blame] | 1405 | |
| 1406 | * :func:`~ssl.RAND_bytes`: generate cryptographically strong |
| 1407 | pseudo-random bytes. |
| 1408 | * :func:`~ssl.RAND_pseudo_bytes`: generate pseudo-random bytes. |
| 1409 | |
Antoine Pitrou | 2c0a967 | 2011-11-17 02:09:13 +0100 | [diff] [blame] | 1410 | (Contributed by Victor Stinner in :issue:`12049`) |
| 1411 | |
| 1412 | * The :mod:`ssl` module now exposes a finer-grained exception hierarchy |
| 1413 | in order to make it easier to inspect the various kinds of errors. |
| 1414 | |
| 1415 | (Contributed by Antoine Pitrou in :issue:`11183`) |
| 1416 | |
| 1417 | * :meth:`~ssl.SSLContext.load_cert_chain` now accepts a *password* argument |
| 1418 | to be used if the private key is encrypted. |
| 1419 | |
| 1420 | (Contributed by Adam Simpkins in :issue:`12803`) |
| 1421 | |
Antoine Pitrou | 73fc814 | 2011-12-23 20:58:36 +0100 | [diff] [blame] | 1422 | * Diffie-Hellman key exchange, both regular and Elliptic Curve-based, is |
| 1423 | now supported through the :meth:`~ssl.SSLContext.load_dh_params` and |
| 1424 | :meth:`~ssl.SSLContext.set_ecdh_curve` methods. |
| 1425 | |
| 1426 | (Contributed by Antoine Pitrou in :issue:`13626` and :issue:`13627`) |
| 1427 | |
Antoine Pitrou | 2c0a967 | 2011-11-17 02:09:13 +0100 | [diff] [blame] | 1428 | * SSL sockets have a new :meth:`~ssl.SSLSocket.get_channel_binding` method |
| 1429 | allowing the implementation of certain authentication mechanisms such as |
| 1430 | SCRAM-SHA-1-PLUS. |
| 1431 | |
| 1432 | (Contributed by Jacek Konieczny in :issue:`12551`) |
| 1433 | |
Antoine Pitrou | 73fc814 | 2011-12-23 20:58:36 +0100 | [diff] [blame] | 1434 | * You can query the SSL compression algorithm used by an SSL socket, thanks |
| 1435 | to its new :meth:`~ssl.SSLSocket.compression` method. |
| 1436 | |
| 1437 | (Contributed by Antoine Pitrou in :issue:`13634`) |
| 1438 | |
Antoine Pitrou | 9a86447 | 2012-05-04 23:15:47 +0200 | [diff] [blame] | 1439 | * Support has been added for the Next Procotol Negotiation extension using |
| 1440 | the :meth:`ssl.SSLContext.set_npn_protocols` method. |
| 1441 | |
| 1442 | (Contributed by Colin Marc in :issue:`14204`) |
| 1443 | |
Antoine Pitrou | ad09b5d | 2012-06-24 22:41:33 +0200 | [diff] [blame] | 1444 | * SSL errors can now be introspected more easily thanks to |
| 1445 | :attr:`~ssl.SSLError.library` and :attr:`~ssl.SSLError.reason` attributes. |
| 1446 | |
| 1447 | (Contributed by Antoine Pitrou in :issue:`14837`) |
| 1448 | |
Giampaolo Rodola' | ffa1d0b | 2012-05-15 15:30:25 +0200 | [diff] [blame] | 1449 | stat |
| 1450 | ---- |
| 1451 | |
| 1452 | - The undocumented tarfile.filemode function has been moved to |
| 1453 | :func:`stat.filemode`. It can be used to convert a file's mode to a string of |
| 1454 | the form '-rwxrwxrwx'. |
| 1455 | |
| 1456 | (Contributed by Giampaolo Rodolà in :issue:`14807`) |
Antoine Pitrou | 73fc814 | 2011-12-23 20:58:36 +0100 | [diff] [blame] | 1457 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1458 | sys |
| 1459 | --- |
Giampaolo Rodola' | 210e7ca | 2011-07-01 13:55:36 +0200 | [diff] [blame] | 1460 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1461 | * The :mod:`sys` module has a new :data:`~sys.thread_info` :term:`struct |
| 1462 | sequence` holding informations about the thread implementation. |
Giampaolo Rodola' | 210e7ca | 2011-07-01 13:55:36 +0200 | [diff] [blame] | 1463 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1464 | (:issue:`11223`) |
Giampaolo Rodola' | 096dcb1 | 2011-06-27 11:17:51 +0200 | [diff] [blame] | 1465 | |
Nick Coghlan | 4fae8cd | 2012-06-11 23:07:51 +1000 | [diff] [blame] | 1466 | textwrap |
| 1467 | -------- |
| 1468 | |
| 1469 | * The :mod:`textwrap` module has a new :func:`~textwrap.indent` that makes |
| 1470 | it straightforward to add a common prefix to selected lines in a block |
| 1471 | of text. |
| 1472 | |
| 1473 | (:issue:`13857`) |
Antoine Pitrou | 5a8bc6f | 2011-11-17 02:20:48 +0100 | [diff] [blame] | 1474 | |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1475 | time |
| 1476 | ---- |
Antoine Pitrou | 5a8bc6f | 2011-11-17 02:20:48 +0100 | [diff] [blame] | 1477 | |
Victor Stinner | ec89539 | 2012-04-29 02:41:27 +0200 | [diff] [blame] | 1478 | The :pep:`418` added new functions to the :mod:`time` module: |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1479 | |
Victor Stinner | ec89539 | 2012-04-29 02:41:27 +0200 | [diff] [blame] | 1480 | * :func:`~time.get_clock_info`: Get information on a clock. |
| 1481 | * :func:`~time.monotonic`: Monotonic clock (cannot go backward), not affected |
| 1482 | by system clock updates. |
| 1483 | * :func:`~time.perf_counter`: Performance counter with the highest available |
| 1484 | resolution to measure a short duration. |
| 1485 | * :func:`~time.process_time`: Sum of the system and user CPU time of the |
| 1486 | current process. |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1487 | |
Victor Stinner | ec89539 | 2012-04-29 02:41:27 +0200 | [diff] [blame] | 1488 | Other new functions: |
| 1489 | |
| 1490 | * :func:`~time.clock_getres`, :func:`~time.clock_gettime` and |
| 1491 | :func:`~time.clock_settime` functions with ``CLOCK_xxx`` constants. |
| 1492 | (Contributed by Victor Stinner in :issue:`10278`) |
Victor Stinner | f4c54ff | 2012-02-08 01:48:34 +0100 | [diff] [blame] | 1493 | |
Antoine Pitrou | 5a8bc6f | 2011-11-17 02:20:48 +0100 | [diff] [blame] | 1494 | |
Victor Stinner | 0db176f | 2012-04-16 00:16:30 +0200 | [diff] [blame] | 1495 | types |
| 1496 | ----- |
| 1497 | |
| 1498 | Add a new :class:`types.MappingProxyType` class: Read-only proxy of a mapping. |
| 1499 | (:issue:`14386`) |
| 1500 | |
| 1501 | |
Nick Coghlan | 7fc570a | 2012-05-20 02:34:13 +1000 | [diff] [blame] | 1502 | The new functions `types.new_class` and `types.prepare_class` provide support |
| 1503 | for PEP 3115 compliant dynamic type creation. (:issue:`14588`) |
| 1504 | |
| 1505 | |
Senthil Kumaran | de49d64 | 2011-10-16 23:54:44 +0800 | [diff] [blame] | 1506 | urllib |
| 1507 | ------ |
| 1508 | |
| 1509 | The :class:`~urllib.request.Request` class, now accepts a *method* argument |
| 1510 | used by :meth:`~urllib.request.Request.get_method` to determine what HTTP method |
Senthil Kumaran | a41c942 | 2011-10-20 02:37:08 +0800 | [diff] [blame] | 1511 | should be used. For example, this will send a ``'HEAD'`` request:: |
Senthil Kumaran | de49d64 | 2011-10-16 23:54:44 +0800 | [diff] [blame] | 1512 | |
| 1513 | >>> urlopen(Request('http://www.python.org', method='HEAD')) |
| 1514 | |
| 1515 | (:issue:`1673007`) |
Giampaolo Rodola' | 096dcb1 | 2011-06-27 11:17:51 +0200 | [diff] [blame] | 1516 | |
Giampaolo Rodola' | be55d99 | 2011-11-22 13:33:34 +0100 | [diff] [blame] | 1517 | |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 1518 | webbrowser |
| 1519 | ---------- |
| 1520 | |
| 1521 | The :mod:`webbrowser` module supports more browsers: Google Chrome (named |
| 1522 | :program:`chrome`, :program:`chromium`, :program:`chrome-browser` or |
| 1523 | :program:`chromium-browser` depending on the version and operating system) as |
| 1524 | well as the the generic launchers :program:`xdg-open` from the FreeDesktop.org |
| 1525 | project and :program:`gvfs-open` which is the default URI handler for GNOME 3. |
| 1526 | |
| 1527 | (:issue:`13620` and :issue:`14493`) |
| 1528 | |
| 1529 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1530 | Optimizations |
| 1531 | ============= |
| 1532 | |
| 1533 | Major performance enhancements have been added: |
| 1534 | |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 1535 | * Thanks to :pep:`393`, some operations on Unicode strings have been optimized: |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1536 | |
| 1537 | * the memory footprint is divided by 2 to 4 depending on the text |
Victor Stinner | a996f1e | 2011-11-21 13:14:43 +0100 | [diff] [blame] | 1538 | * encode an ASCII string to UTF-8 doesn't need to encode characters anymore, |
| 1539 | the UTF-8 representation is shared with the ASCII representation |
Victor Stinner | 6099a03 | 2011-12-18 14:22:26 +0100 | [diff] [blame] | 1540 | * the UTF-8 encoder has been optimized |
| 1541 | * repeating a single ASCII letter and getting a substring of a ASCII strings |
| 1542 | is 4 times faster |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1543 | |
Antoine Pitrou | 5d7e1d3 | 2012-06-24 22:38:23 +0200 | [diff] [blame] | 1544 | * UTF-8 is now 2x to 4x faster. UTF-16 encoding is now up to 10x faster. |
Antoine Pitrou | 5cec9d2 | 2012-05-17 17:37:02 +0200 | [diff] [blame] | 1545 | |
Antoine Pitrou | c909296 | 2012-06-15 22:22:18 +0200 | [diff] [blame] | 1546 | (contributed by Serhiy Storchaka, :issue:`14624`, :issue:`14738` and |
| 1547 | :issue:`15026`.) |
Antoine Pitrou | 5cec9d2 | 2012-05-17 17:37:02 +0200 | [diff] [blame] | 1548 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1549 | |
| 1550 | Build and C API Changes |
| 1551 | ======================= |
| 1552 | |
| 1553 | Changes to Python's build process and to the C API include: |
| 1554 | |
Stefan Krah | 95b1ba6 | 2012-02-29 17:27:21 +0100 | [diff] [blame] | 1555 | * New :pep:`3118` related function: |
| 1556 | |
| 1557 | * :c:func:`PyMemoryView_FromMemory` |
| 1558 | |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 1559 | * :pep:`393` added new Unicode types, macros and functions: |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1560 | |
Victor Stinner | a996f1e | 2011-11-21 13:14:43 +0100 | [diff] [blame] | 1561 | * High-level API: |
| 1562 | |
| 1563 | * :c:func:`PyUnicode_CopyCharacters` |
| 1564 | * :c:func:`PyUnicode_FindChar` |
| 1565 | * :c:func:`PyUnicode_GetLength`, :c:macro:`PyUnicode_GET_LENGTH` |
| 1566 | * :c:func:`PyUnicode_New` |
| 1567 | * :c:func:`PyUnicode_Substring` |
| 1568 | * :c:func:`PyUnicode_ReadChar`, :c:func:`PyUnicode_WriteChar` |
| 1569 | |
| 1570 | * Low-level API: |
| 1571 | |
| 1572 | * :c:type:`Py_UCS1`, :c:type:`Py_UCS2`, :c:type:`Py_UCS4` types |
| 1573 | * :c:type:`PyASCIIObject` and :c:type:`PyCompactUnicodeObject` structures |
| 1574 | * :c:macro:`PyUnicode_READY` |
| 1575 | * :c:func:`PyUnicode_FromKindAndData` |
| 1576 | * :c:func:`PyUnicode_AsUCS4`, :c:func:`PyUnicode_AsUCS4Copy` |
| 1577 | * :c:macro:`PyUnicode_DATA`, :c:macro:`PyUnicode_1BYTE_DATA`, |
| 1578 | :c:macro:`PyUnicode_2BYTE_DATA`, :c:macro:`PyUnicode_4BYTE_DATA` |
| 1579 | * :c:macro:`PyUnicode_KIND` with :c:type:`PyUnicode_Kind` enum: |
| 1580 | :c:data:`PyUnicode_WCHAR_KIND`, :c:data:`PyUnicode_1BYTE_KIND`, |
| 1581 | :c:data:`PyUnicode_2BYTE_KIND`, :c:data:`PyUnicode_4BYTE_KIND` |
| 1582 | * :c:macro:`PyUnicode_READ`, :c:macro:`PyUnicode_READ_CHAR`, :c:macro:`PyUnicode_WRITE` |
| 1583 | * :c:macro:`PyUnicode_MAX_CHAR_VALUE` |
| 1584 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1585 | |
| 1586 | |
Victor Stinner | d1be878 | 2011-12-09 00:10:41 +0100 | [diff] [blame] | 1587 | Deprecated |
| 1588 | ========== |
| 1589 | |
Georg Brandl | 0cd25c9 | 2011-04-29 13:45:54 +0200 | [diff] [blame] | 1590 | Unsupported Operating Systems |
Victor Stinner | d1be878 | 2011-12-09 00:10:41 +0100 | [diff] [blame] | 1591 | ----------------------------- |
Victor Stinner | b90db4c | 2011-04-26 22:48:24 +0200 | [diff] [blame] | 1592 | |
Brian Curtin | 49a40cd | 2011-05-02 22:30:06 -0500 | [diff] [blame] | 1593 | OS/2 and VMS are no longer supported due to the lack of a maintainer. |
| 1594 | |
| 1595 | Windows 2000 and Windows platforms which set ``COMSPEC`` to ``command.com`` |
| 1596 | are no longer supported due to maintenance burden. |
Victor Stinner | b90db4c | 2011-04-26 22:48:24 +0200 | [diff] [blame] | 1597 | |
| 1598 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1599 | Deprecated Python modules, functions and methods |
Victor Stinner | d1be878 | 2011-12-09 00:10:41 +0100 | [diff] [blame] | 1600 | ------------------------------------------------ |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1601 | |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1602 | * The ``unicode_internal`` codec has been deprecated because of the |
Sandro Tosi | cd89912 | 2012-01-22 12:16:04 +0100 | [diff] [blame] | 1603 | :pep:`393`, use UTF-8, UTF-16 (``utf-16-le`` or ``utf-16-be``), or UTF-32 |
| 1604 | (``utf-32-le`` or ``utf-32-be``) |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1605 | * :meth:`ftplib.FTP.nlst` and :meth:`ftplib.FTP.dir`: use |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1606 | :meth:`ftplib.FTP.mlsd` |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1607 | * :func:`platform.popen`: use the :mod:`subprocess` module. Check especially |
| 1608 | the :ref:`subprocess-replacements` section. |
| 1609 | * :issue:`13374`: The Windows bytes API has been deprecated in the :mod:`os` |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1610 | module. Use Unicode filenames, instead of bytes filenames, to not depend on |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1611 | the ANSI code page anymore and to support any filename. |
Florent Xicluna | a72a98f | 2012-02-13 11:03:30 +0100 | [diff] [blame] | 1612 | * :issue:`13988`: The :mod:`xml.etree.cElementTree` module is deprecated. The |
| 1613 | accelerator is used automatically whenever available. |
Victor Stinner | 47620a6 | 2012-04-29 02:52:39 +0200 | [diff] [blame] | 1614 | * The behaviour of :func:`time.clock` depends on the platform: use the new |
| 1615 | :func:`time.perf_counter` or :func:`time.process_time` function instead, |
| 1616 | depending on your requirements, to have a well defined behaviour. |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1617 | |
| 1618 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1619 | Deprecated functions and types of the C API |
Victor Stinner | d1be878 | 2011-12-09 00:10:41 +0100 | [diff] [blame] | 1620 | ------------------------------------------- |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1621 | |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 1622 | The :c:type:`Py_UNICODE` has been deprecated by :pep:`393` and will be |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1623 | removed in Python 4. All functions using this type are deprecated: |
| 1624 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1625 | Unicode functions and methods using :c:type:`Py_UNICODE` and |
| 1626 | :c:type:`Py_UNICODE*` types: |
| 1627 | |
| 1628 | * :c:macro:`PyUnicode_FromUnicode`: use :c:func:`PyUnicode_FromWideChar` or |
| 1629 | :c:func:`PyUnicode_FromKindAndData` |
| 1630 | * :c:macro:`PyUnicode_AS_UNICODE`, :c:func:`PyUnicode_AsUnicode`, |
| 1631 | :c:func:`PyUnicode_AsUnicodeAndSize`: use :c:func:`PyUnicode_AsWideCharString` |
| 1632 | * :c:macro:`PyUnicode_AS_DATA`: use :c:macro:`PyUnicode_DATA` with |
| 1633 | :c:macro:`PyUnicode_READ` and :c:macro:`PyUnicode_WRITE` |
| 1634 | * :c:macro:`PyUnicode_GET_SIZE`, :c:func:`PyUnicode_GetSize`: use |
| 1635 | :c:macro:`PyUnicode_GET_LENGTH` or :c:func:`PyUnicode_GetLength` |
| 1636 | * :c:macro:`PyUnicode_GET_DATA_SIZE`: use |
| 1637 | ``PyUnicode_GET_LENGTH(str) * PyUnicode_KIND(str)`` (only work on ready |
| 1638 | strings) |
Victor Stinner | bf6e560 | 2011-12-12 01:53:47 +0100 | [diff] [blame] | 1639 | * :c:func:`PyUnicode_AsUnicodeCopy`: use :c:func:`PyUnicode_AsUCS4Copy` or |
| 1640 | :c:func:`PyUnicode_AsWideCharString` |
Victor Stinner | ab59594 | 2011-12-17 04:59:06 +0100 | [diff] [blame] | 1641 | * :c:func:`PyUnicode_GetMax` |
| 1642 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1643 | |
Victor Stinner | a996f1e | 2011-11-21 13:14:43 +0100 | [diff] [blame] | 1644 | Functions and macros manipulating Py_UNICODE* strings: |
| 1645 | |
| 1646 | * :c:macro:`Py_UNICODE_strlen`: use :c:func:`PyUnicode_GetLength` or |
| 1647 | :c:macro:`PyUnicode_GET_LENGTH` |
| 1648 | * :c:macro:`Py_UNICODE_strcat`: use :c:func:`PyUnicode_CopyCharacters` or |
| 1649 | :c:func:`PyUnicode_FromFormat` |
| 1650 | * :c:macro:`Py_UNICODE_strcpy`, :c:macro:`Py_UNICODE_strncpy`, |
| 1651 | :c:macro:`Py_UNICODE_COPY`: use :c:func:`PyUnicode_CopyCharacters` or |
| 1652 | :c:func:`PyUnicode_Substring` |
| 1653 | * :c:macro:`Py_UNICODE_strcmp`: use :c:func:`PyUnicode_Compare` |
| 1654 | * :c:macro:`Py_UNICODE_strncmp`: use :c:func:`PyUnicode_Tailmatch` |
| 1655 | * :c:macro:`Py_UNICODE_strchr`, :c:macro:`Py_UNICODE_strrchr`: use |
| 1656 | :c:func:`PyUnicode_FindChar` |
Victor Stinner | 606e19d | 2012-01-04 03:59:16 +0100 | [diff] [blame] | 1657 | * :c:macro:`Py_UNICODE_FILL`: use :c:func:`PyUnicode_Fill` |
Victor Stinner | ab59594 | 2011-12-17 04:59:06 +0100 | [diff] [blame] | 1658 | * :c:macro:`Py_UNICODE_MATCH` |
Victor Stinner | a996f1e | 2011-11-21 13:14:43 +0100 | [diff] [blame] | 1659 | |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1660 | Encoders: |
| 1661 | |
| 1662 | * :c:func:`PyUnicode_Encode`: use :c:func:`PyUnicode_AsEncodedObject` |
| 1663 | * :c:func:`PyUnicode_EncodeUTF7` |
Victor Stinner | a996f1e | 2011-11-21 13:14:43 +0100 | [diff] [blame] | 1664 | * :c:func:`PyUnicode_EncodeUTF8`: use :c:func:`PyUnicode_AsUTF8` or |
| 1665 | :c:func:`PyUnicode_AsUTF8String` |
Victor Stinner | 46606ce | 2011-11-20 18:27:55 +0100 | [diff] [blame] | 1666 | * :c:func:`PyUnicode_EncodeUTF32` |
| 1667 | * :c:func:`PyUnicode_EncodeUTF16` |
| 1668 | * :c:func:`PyUnicode_EncodeUnicodeEscape:` use |
| 1669 | :c:func:`PyUnicode_AsUnicodeEscapeString` |
| 1670 | * :c:func:`PyUnicode_EncodeRawUnicodeEscape:` use |
| 1671 | :c:func:`PyUnicode_AsRawUnicodeEscapeString` |
| 1672 | * :c:func:`PyUnicode_EncodeLatin1`: use :c:func:`PyUnicode_AsLatin1String` |
| 1673 | * :c:func:`PyUnicode_EncodeASCII`: use :c:func:`PyUnicode_AsASCIIString` |
| 1674 | * :c:func:`PyUnicode_EncodeCharmap` |
| 1675 | * :c:func:`PyUnicode_TranslateCharmap` |
| 1676 | * :c:func:`PyUnicode_EncodeMBCS`: use :c:func:`PyUnicode_AsMBCSString` or |
| 1677 | :c:func:`PyUnicode_EncodeCodePage` (with ``CP_ACP`` code_page) |
| 1678 | * :c:func:`PyUnicode_EncodeDecimal`, |
| 1679 | :c:func:`PyUnicode_TransformDecimalToASCII` |
| 1680 | |
| 1681 | |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1682 | Porting to Python 3.3 |
| 1683 | ===================== |
| 1684 | |
| 1685 | This section lists previously described changes and other bugfixes |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1686 | that may require changes to your code. |
| 1687 | |
Barry Warsaw | c1e721b | 2012-07-30 16:24:12 -0400 | [diff] [blame] | 1688 | .. _portingpythoncode: |
| 1689 | |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1690 | Porting Python code |
| 1691 | ------------------- |
Giampaolo Rodolà | 3108f98 | 2011-02-24 20:59:48 +0000 | [diff] [blame] | 1692 | |
Georg Brandl | d6c4340 | 2012-03-07 08:55:52 +0100 | [diff] [blame] | 1693 | .. XXX add a point about hash randomization and that it's always on in 3.3 |
| 1694 | |
Victor Stinner | 19bd069 | 2011-11-16 00:18:57 +0100 | [diff] [blame] | 1695 | * :issue:`12326`: On Linux, sys.platform doesn't contain the major version |
Victor Stinner | ff3d939 | 2011-08-20 23:39:26 +0200 | [diff] [blame] | 1696 | anymore. It is now always 'linux', instead of 'linux2' or 'linux3' depending |
| 1697 | on the Linux version used to build Python. Replace sys.platform == 'linux2' |
| 1698 | with sys.platform.startswith('linux'), or directly sys.platform == 'linux' if |
| 1699 | you don't need to support older Python versions. |
Éric Araujo | c09fca6 | 2011-03-23 02:06:24 +0100 | [diff] [blame] | 1700 | |
Victor Stinner | ecc6e66 | 2012-03-14 00:39:29 +0100 | [diff] [blame] | 1701 | * :issue:`13847`, :issue:`14180`: :mod:`time` and :mod:`datetime`: |
| 1702 | :exc:`OverflowError` is now raised instead of :exc:`ValueError` if a |
| 1703 | timestamp is out of range. :exc:`OSError` is now raised if C functions |
| 1704 | :c:func:`gmtime` or :c:func:`localtime` failed. |
| 1705 | |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 1706 | * The default finders used by import now utilize a cache of what is contained |
| 1707 | within a specific directory. If you create a Python source file or sourceless |
| 1708 | bytecode file, make sure to call :func:`importlib.invalidate_caches` to clear |
| 1709 | out the cache for the finders to notice the new file. |
| 1710 | |
| 1711 | * :exc:`ImportError` now uses the full name of the module that was attemped to |
| 1712 | be imported. Doctests that check ImportErrors' message will need to be |
| 1713 | updated to use the full name of the module instead of just the tail of the |
| 1714 | name. |
| 1715 | |
| 1716 | * The **index** argument to :func:`__import__` now defaults to 0 instead of -1 |
| 1717 | and no longer support negative values. It was an oversight when :pep:`328` was |
| 1718 | implemented that the default value remained -1. If you need to continue to |
| 1719 | perform a relative import followed by an absolute import, then perform the |
| 1720 | relative import using an index of 1, followed by another import using an |
| 1721 | index of 0. It is preferred, though, that you use |
| 1722 | :func:`importlib.import_module` rather than call :func:`__import__` directly. |
| 1723 | |
| 1724 | * :func:`__import__` no longer allows one to use an index value other than 0 |
| 1725 | for top-level modules. E.g. ``__import__('sys', level=1)`` is now an error. |
| 1726 | |
| 1727 | * Because :attr:`sys.meta_path` and :attr:`sys.path_hooks` now have finders on |
| 1728 | them by default, you will most likely want to use :meth:`list.insert` instead |
| 1729 | of :meth:`list.append` to add to those lists. |
| 1730 | |
| 1731 | * Because ``None`` is now inserted into :attr:`sys.path_importer_cache`, if you |
| 1732 | are clearing out entries in the dictionary of paths that do not have a |
| 1733 | finder, you will need to remove keys paired with values of ``None`` **and** |
Brett Cannon | 903c27c | 2012-07-09 14:15:32 -0400 | [diff] [blame] | 1734 | :class:`imp.NullImporter` to be backwards-compatible. This will lead to extra |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 1735 | overhead on older versions of Python that re-insert ``None`` into |
| 1736 | :attr:`sys.path_importer_cache` where it repesents the use of implicit |
| 1737 | finders, but semantically it should not change anything. |
| 1738 | |
| 1739 | * :meth:`importlib.abc.SourceLoader.path_mtime` is now deprecated in favour of |
| 1740 | :meth:`importlib.abc.SourceLoader.path_stats` as bytecode files now store |
| 1741 | both the modification time and size of the source file the bytecode file was |
| 1742 | compiled from. |
| 1743 | |
Brett Cannon | 077ef45 | 2012-08-02 17:50:06 -0400 | [diff] [blame^] | 1744 | * :class:`importlib.abc.Finder` no longer specifies a `find_module()` abstract |
| 1745 | method that must be implemented. If you were relying on subclasses to |
| 1746 | implement that method, make sure to check for the method's existence first. |
| 1747 | You will probably want to check for `find_loader()` first, though, in the |
| 1748 | case of working with :term:`path entry finders <path entry finder>`. |
| 1749 | |
Nick Coghlan | 6061000 | 2012-07-15 22:39:39 +1000 | [diff] [blame] | 1750 | * :mod:`pkgutil` has been converted to use :mod:`importlib` internally. This |
| 1751 | eliminates many edge cases where the old behaviour of the PEP 302 import |
| 1752 | emulation failed to match the behaviour of the real import system. The |
| 1753 | import emulation itself is still present, but is now deprecated. The |
| 1754 | :func:`pkgutil.iter_importers` and :func:`pkgutil.walk_packages` functions |
| 1755 | special case the standard import hooks so they are still supported even |
| 1756 | though they do not provide the non-standard ``iter_modules()`` method. |
Brett Cannon | 903c27c | 2012-07-09 14:15:32 -0400 | [diff] [blame] | 1757 | |
Brett Cannon | c204348 | 2012-04-29 20:59:41 -0400 | [diff] [blame] | 1758 | |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1759 | Porting C code |
| 1760 | -------------- |
| 1761 | |
Stefan Krah | 54c3203 | 2012-02-29 17:47:21 +0100 | [diff] [blame] | 1762 | * In the course of changes to the buffer API the undocumented |
| 1763 | :c:member:`~Py_buffer.smalltable` member of the |
| 1764 | :c:type:`Py_buffer` structure has been removed and the |
| 1765 | layout of the :c:type:`PyMemoryViewObject` has changed. |
| 1766 | |
| 1767 | All extensions relying on the relevant parts in ``memoryobject.h`` |
| 1768 | or ``object.h`` must be rebuilt. |
| 1769 | |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1770 | * Due to :ref:`PEP 393 <pep-393>`, the :c:type:`Py_UNICODE` type and all |
| 1771 | functions using this type are deprecated (but will stay available for |
| 1772 | at least five years). If you were using low-level Unicode APIs to |
| 1773 | construct and access unicode objects and you want to benefit of the |
Éric Araujo | 4f61a2d | 2012-04-04 23:01:01 -0400 | [diff] [blame] | 1774 | memory footprint reduction provided by PEP 393, you have to convert |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1775 | your code to the new :doc:`Unicode API <../c-api/unicode>`. |
| 1776 | |
| 1777 | However, if you only have been using high-level functions such as |
| 1778 | :c:func:`PyUnicode_Concat()`, :c:func:`PyUnicode_Join` or |
| 1779 | :c:func:`PyUnicode_FromFormat()`, your code will automatically take |
| 1780 | advantage of the new unicode representations. |
| 1781 | |
Brett Cannon | 77b2abd | 2012-07-09 16:09:00 -0400 | [diff] [blame] | 1782 | * :c:func:`PyImport_GetMagicNumber` now returns -1 upon failure. |
| 1783 | |
| 1784 | |
Antoine Pitrou | c229e6e | 2012-02-20 19:41:11 +0100 | [diff] [blame] | 1785 | Building C extensions |
| 1786 | --------------------- |
| 1787 | |
| 1788 | * The range of possible file names for C extensions has been narrowed. |
| 1789 | Very rarely used spellings have been suppressed: under POSIX, files |
| 1790 | named ``xxxmodule.so``, ``xxxmodule.abi3.so`` and |
| 1791 | ``xxxmodule.cpython-*.so`` are no longer recognized as implementing |
| 1792 | the ``xxx`` module. If you had been generating such files, you have |
| 1793 | to switch to the other spellings (i.e., remove the ``module`` string |
| 1794 | from the file names). |
| 1795 | |
| 1796 | (implemented in :issue:`14040`.) |
| 1797 | |
| 1798 | |
Antoine Pitrou | 037ffbf | 2011-10-24 00:25:41 +0200 | [diff] [blame] | 1799 | Other issues |
| 1800 | ------------ |
| 1801 | |
Éric Araujo | c09fca6 | 2011-03-23 02:06:24 +0100 | [diff] [blame] | 1802 | .. Issue #11591: When :program:`python` was started with :option:`-S`, |
| 1803 | ``import site`` will not add site-specific paths to the module search |
| 1804 | paths. In previous versions, it did. See changeset for doc changes in |
| 1805 | various files. Contributed by Carl Meyer with editions by Éric Araujo. |
Éric Araujo | be3bd57 | 2011-03-26 01:55:15 +0100 | [diff] [blame] | 1806 | |
Éric Araujo | bfc9729 | 2011-11-14 18:18:15 +0100 | [diff] [blame] | 1807 | .. Issue #10998: the -Q command-line flag and related artifacts have been |
Éric Araujo | be3bd57 | 2011-03-26 01:55:15 +0100 | [diff] [blame] | 1808 | removed. Code checking sys.flags.division_warning will need updating. |
| 1809 | Contributed by Éric Araujo. |