Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 1 | **************************** |
| 2 | What's New In Python 3.6 |
| 3 | **************************** |
| 4 | |
| 5 | :Release: |release| |
| 6 | :Date: |today| |
| 7 | |
| 8 | .. Rules for maintenance: |
| 9 | |
| 10 | * Anyone can add text to this document. Do not spend very much time |
| 11 | on the wording of your changes, because your text will probably |
| 12 | get rewritten to some degree. |
| 13 | |
| 14 | * The maintainer will go through Misc/NEWS periodically and add |
| 15 | changes; it's therefore more important to add your changes to |
| 16 | Misc/NEWS than to this file. |
| 17 | |
| 18 | * This is not a complete list of every single change; completeness |
| 19 | is the purpose of Misc/NEWS. Some changes I consider too small |
| 20 | or esoteric to include. If such a change is added to the text, |
| 21 | I'll just remove it. (This is another reason you shouldn't spend |
| 22 | too much time on writing your addition.) |
| 23 | |
| 24 | * If you want to draw your new text to the attention of the |
| 25 | maintainer, add 'XXX' to the beginning of the paragraph or |
| 26 | section. |
| 27 | |
| 28 | * It's OK to just add a fragmentary note about a change. For |
| 29 | example: "XXX Describe the transmogrify() function added to the |
| 30 | socket module." The maintainer will research the change and |
| 31 | write the necessary text. |
| 32 | |
| 33 | * You can comment out your additions if you like, but it's not |
| 34 | necessary (especially when a final release is some months away). |
| 35 | |
| 36 | * Credit the author of a patch or bugfix. Just the name is |
| 37 | sufficient; the e-mail address isn't necessary. |
| 38 | |
| 39 | * It's helpful to add the bug/patch number as a comment: |
| 40 | |
| 41 | XXX Describe the transmogrify() function added to the socket |
| 42 | module. |
| 43 | (Contributed by P.Y. Developer in :issue:`12345`.) |
| 44 | |
| 45 | This saves the maintainer the effort of going through the Mercurial log |
| 46 | when researching a change. |
| 47 | |
| 48 | This article explains the new features in Python 3.6, compared to 3.5. |
| 49 | |
| 50 | For full details, see the :source:`Misc/NEWS` file. |
| 51 | |
| 52 | .. note:: |
| 53 | |
| 54 | Prerelease users should be aware that this document is currently in draft |
| 55 | form. It will be updated substantially as Python 3.6 moves towards release, |
| 56 | so it's worth checking back even after reading earlier versions. |
| 57 | |
| 58 | |
| 59 | Summary -- Release highlights |
| 60 | ============================= |
| 61 | |
| 62 | .. This section singles out the most important changes in Python 3.6. |
| 63 | Brevity is key. |
| 64 | |
Martin Panter | bc1ee46 | 2016-02-13 00:41:37 +0000 | [diff] [blame] | 65 | * PEP 498: :ref:`Formatted string literals <whatsnew-fstrings>` |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 66 | |
| 67 | .. PEP-sized items next. |
| 68 | |
| 69 | .. _pep-4XX: |
| 70 | |
| 71 | .. PEP 4XX: Virtual Environments |
| 72 | .. ============================= |
| 73 | |
| 74 | |
| 75 | .. (Implemented by Foo Bar.) |
| 76 | |
| 77 | .. .. seealso:: |
| 78 | |
| 79 | :pep:`4XX` - Python Virtual Environments |
| 80 | PEP written by Carl Meyer |
| 81 | |
| 82 | |
Victor Stinner | 34be807 | 2016-03-14 12:04:26 +0100 | [diff] [blame] | 83 | New Features |
| 84 | ============ |
| 85 | |
Martin Panter | bc1ee46 | 2016-02-13 00:41:37 +0000 | [diff] [blame] | 86 | .. _whatsnew-fstrings: |
| 87 | |
| 88 | PEP 498: Formatted string literals |
| 89 | ---------------------------------- |
| 90 | |
| 91 | Formatted string literals are a new kind of string literal, prefixed |
| 92 | with ``'f'``. They are similar to the format strings accepted by |
| 93 | :meth:`str.format`. They contain replacement fields surrounded by |
| 94 | curly braces. The replacement fields are expressions, which are |
| 95 | evaluated at run time, and then formatted using the :func:`format` protocol. |
| 96 | |
| 97 | >>> name = "Fred" |
| 98 | >>> f"He said his name is {name}." |
| 99 | 'He said his name is Fred.' |
| 100 | |
| 101 | See :pep:`498` and the main documentation at :ref:`f-strings`. |
| 102 | |
| 103 | |
Victor Stinner | 34be807 | 2016-03-14 12:04:26 +0100 | [diff] [blame] | 104 | PYTHONMALLOC environment variable |
| 105 | --------------------------------- |
| 106 | |
| 107 | The new :envvar:`PYTHONMALLOC` environment variable allows to set the Python |
| 108 | memory allocators and/or install debug hooks. |
| 109 | |
| 110 | It is now possible to install debug hooks on Python memory allocators on Python |
| 111 | compiled in release mode using ``PYTHONMALLOC=debug``. Effects of debug hooks: |
| 112 | |
| 113 | * Newly allocated memory is filled with the byte ``0xCB`` |
| 114 | * Freed memory is filled with the byte ``0xDB`` |
| 115 | * Detect violations of Python memory allocator API. For example, |
| 116 | :c:func:`PyObject_Free` called on a memory block allocated by |
| 117 | :c:func:`PyMem_Malloc`. |
| 118 | * Detect write before the start of the buffer (buffer underflow) |
| 119 | * Detect write after the end of the buffer (buffer overflow) |
Victor Stinner | c4aec36 | 2016-03-14 22:26:53 +0100 | [diff] [blame^] | 120 | * Check that the :term:`GIL <global interpreter lock>` is held when allocator |
| 121 | functions of the :c:data:`PYMEM_DOMAIN_OBJ` domain (ex: |
| 122 | :c:func:`PyObject_Malloc`) are called |
Victor Stinner | 34be807 | 2016-03-14 12:04:26 +0100 | [diff] [blame] | 123 | |
| 124 | See the :c:func:`PyMem_SetupDebugHooks` function for debug hooks on Python |
| 125 | memory allocators. |
| 126 | |
| 127 | It is now also possible to force the usage of the :c:func:`malloc` allocator of |
| 128 | the C library for all Python memory allocations using ``PYTHONMALLOC=malloc``. |
| 129 | It helps to use external memory debuggers like Valgrind on a Python compiled in |
| 130 | release mode. |
| 131 | |
| 132 | (Contributed by Victor Stinner in :issue:`26516`.) |
| 133 | |
| 134 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 135 | Other Language Changes |
| 136 | ====================== |
| 137 | |
| 138 | * None yet. |
| 139 | |
| 140 | |
| 141 | New Modules |
| 142 | =========== |
| 143 | |
| 144 | * None yet. |
| 145 | |
| 146 | |
| 147 | Improved Modules |
| 148 | ================ |
| 149 | |
Berker Peksag | b6c9572 | 2015-10-08 13:58:49 +0300 | [diff] [blame] | 150 | datetime |
| 151 | -------- |
| 152 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 153 | The :meth:`datetime.strftime() <datetime.datetime.strftime>` and |
| 154 | :meth:`date.strftime() <datetime.date.strftime>` methods now support ISO 8601 date |
Berker Peksag | b6c9572 | 2015-10-08 13:58:49 +0300 | [diff] [blame] | 155 | directives ``%G``, ``%u`` and ``%V``. |
| 156 | (Contributed by Ashley Anderson in :issue:`12006`.) |
| 157 | |
| 158 | |
Serhiy Storchaka | ffe96ae | 2016-02-11 13:21:30 +0200 | [diff] [blame] | 159 | os |
| 160 | -- |
| 161 | |
| 162 | A new :meth:`~os.scandir.close` method allows explicitly closing a |
| 163 | :func:`~os.scandir` iterator. The :func:`~os.scandir` iterator now |
| 164 | supports the :term:`context manager` protocol. If a :func:`scandir` |
| 165 | iterator is neither exhausted nor explicitly closed a :exc:`ResourceWarning` |
| 166 | will be emitted in its destructor. |
| 167 | (Contributed by Serhiy Storchaka in :issue:`25994`.) |
| 168 | |
| 169 | |
Serhiy Storchaka | 0d554d7 | 2015-10-10 22:42:18 +0300 | [diff] [blame] | 170 | pickle |
| 171 | ------ |
| 172 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 173 | Objects that need calling ``__new__`` with keyword arguments can now be pickled |
Serhiy Storchaka | 0d554d7 | 2015-10-10 22:42:18 +0300 | [diff] [blame] | 174 | using :ref:`pickle protocols <pickle-protocols>` older than protocol version 4. |
| 175 | Protocol version 4 already supports this case. (Contributed by Serhiy |
| 176 | Storchaka in :issue:`24164`.) |
| 177 | |
| 178 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 179 | rlcompleter |
| 180 | ----------- |
Serhiy Storchaka | ab82422 | 2015-09-27 13:43:50 +0300 | [diff] [blame] | 181 | |
| 182 | Private and special attribute names now are omitted unless the prefix starts |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 183 | with underscores. A space or a colon is added after some completed keywords. |
Serhiy Storchaka | ab82422 | 2015-09-27 13:43:50 +0300 | [diff] [blame] | 184 | (Contributed by Serhiy Storchaka in :issue:`25011` and :issue:`25209`.) |
| 185 | |
Martin Panter | 6fe3926 | 2015-11-13 23:54:02 +0000 | [diff] [blame] | 186 | Names of most attributes listed by :func:`dir` are now completed. |
| 187 | Previously, names of properties and slots which were not yet created on |
| 188 | an instance were excluded. (Contributed by Martin Panter in :issue:`25590`.) |
| 189 | |
Serhiy Storchaka | ab82422 | 2015-09-27 13:43:50 +0300 | [diff] [blame] | 190 | |
R David Murray | 4f09806 | 2015-11-28 12:24:52 -0500 | [diff] [blame] | 191 | telnetlib |
| 192 | --------- |
| 193 | |
| 194 | :class:`~telnetlib.Telnet` is now a context manager (contributed by |
| 195 | Stéphane Wirtel in :issue:`25485`). |
| 196 | |
| 197 | |
Victor Stinner | 2c2a4e6 | 2016-03-11 22:17:48 +0100 | [diff] [blame] | 198 | unittest.mock |
| 199 | ------------- |
| 200 | |
| 201 | The :class:`~unittest.mock.Mock` class has the following improvements: |
| 202 | |
| 203 | * Two new methods, :meth:`Mock.assert_called() |
| 204 | <unittest.mock.Mock.assert_called>` and :meth:`Mock.assert_called_once() |
| 205 | <unittest.mock.Mock.assert_called_once>` to check if the mock object |
| 206 | was called. |
| 207 | (Contributed by Amit Saha in :issue:`26323`.) |
| 208 | |
| 209 | |
Berker Peksag | 960e848 | 2015-10-08 12:27:06 +0300 | [diff] [blame] | 210 | urllib.robotparser |
| 211 | ------------------ |
| 212 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 213 | :class:`~urllib.robotparser.RobotFileParser` now supports the ``Crawl-delay`` and |
Berker Peksag | 960e848 | 2015-10-08 12:27:06 +0300 | [diff] [blame] | 214 | ``Request-rate`` extensions. |
| 215 | (Contributed by Nikolay Bogoychev in :issue:`16099`.) |
| 216 | |
| 217 | |
Serhiy Storchaka | 503f908 | 2016-02-08 00:02:25 +0200 | [diff] [blame] | 218 | zipfile |
| 219 | ------- |
| 220 | |
| 221 | A new :meth:`ZipInfo.from_file() <zipfile.ZipInfo.from_file>` class method |
Martin Panter | 288ed03 | 2016-02-10 05:45:55 +0000 | [diff] [blame] | 222 | allows making a :class:`~zipfile.ZipInfo` instance from a filesystem file. |
Serhiy Storchaka | 503f908 | 2016-02-08 00:02:25 +0200 | [diff] [blame] | 223 | A new :meth:`ZipInfo.is_dir() <zipfile.ZipInfo.is_dir>` method can be used |
| 224 | to check if the :class:`~zipfile.ZipInfo` instance represents a directory. |
| 225 | (Contributed by Thomas Kluyver in :issue:`26039`.) |
| 226 | |
| 227 | |
Martin Panter | 1fe0d13 | 2016-02-10 10:06:36 +0000 | [diff] [blame] | 228 | zlib |
| 229 | ---- |
| 230 | |
| 231 | The :func:`~zlib.compress` function now accepts keyword arguments. |
| 232 | (Contributed by Aviv Palivoda in :issue:`26243`.) |
| 233 | |
| 234 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 235 | Optimizations |
| 236 | ============= |
| 237 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 238 | * The ASCII decoder is now up to 60 times as fast for error handlers |
Victor Stinner | ebcf9ed | 2015-10-14 10:10:00 +0200 | [diff] [blame] | 239 | ``surrogateescape``, ``ignore`` and ``replace`` (Contributed |
| 240 | by Victor Stinner in :issue:`24870`). |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 241 | |
Terry Jan Reedy | 6dc9ce1 | 2015-10-20 01:07:53 -0400 | [diff] [blame] | 242 | * The ASCII and the Latin1 encoders are now up to 3 times as fast for the |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 243 | error handler ``surrogateescape`` (Contributed by Victor Stinner in :issue:`25227`). |
Victor Stinner | c3713e9 | 2015-09-29 12:32:13 +0200 | [diff] [blame] | 244 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 245 | * The UTF-8 encoder is now up to 75 times as fast for error handlers |
Victor Stinner | ebcf9ed | 2015-10-14 10:10:00 +0200 | [diff] [blame] | 246 | ``ignore``, ``replace``, ``surrogateescape``, ``surrogatepass`` (Contributed |
| 247 | by Victor Stinner in :issue:`25267`). |
Victor Stinner | 01ada39 | 2015-10-01 21:54:51 +0200 | [diff] [blame] | 248 | |
Martin Panter | fad4b60 | 2015-11-14 01:29:17 +0000 | [diff] [blame] | 249 | * The UTF-8 decoder is now up to 15 times as fast for error handlers |
Victor Stinner | ebcf9ed | 2015-10-14 10:10:00 +0200 | [diff] [blame] | 250 | ``ignore``, ``replace`` and ``surrogateescape`` (Contributed |
| 251 | by Victor Stinner in :issue:`25301`). |
| 252 | |
| 253 | * ``bytes % args`` is now up to 2 times faster. (Contributed by Victor Stinner |
| 254 | in :issue:`25349`). |
| 255 | |
| 256 | * ``bytearray % args`` is now between 2.5 and 5 times faster. (Contributed by |
| 257 | Victor Stinner in :issue:`25399`). |
Victor Stinner | 1d65d91 | 2015-10-05 13:43:50 +0200 | [diff] [blame] | 258 | |
Victor Stinner | 2bf8993 | 2015-10-14 11:25:33 +0200 | [diff] [blame] | 259 | * Optimize :meth:`bytes.fromhex` and :meth:`bytearray.fromhex`: they are now |
| 260 | between 2x and 3.5x faster. (Contributed by Victor Stinner in :issue:`25401`). |
| 261 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 262 | |
| 263 | Build and C API Changes |
| 264 | ======================= |
| 265 | |
Martin Panter | b4ce1fc | 2015-11-30 03:18:29 +0000 | [diff] [blame] | 266 | * New :c:func:`Py_FinalizeEx` API which indicates if flushing buffered data |
| 267 | failed (:issue:`5319`). |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 268 | |
| 269 | |
| 270 | Deprecated |
| 271 | ========== |
| 272 | |
Yury Selivanov | 7a21911 | 2015-05-28 17:10:29 -0400 | [diff] [blame] | 273 | New Keywords |
| 274 | ------------ |
| 275 | |
Yury Selivanov | 62f27b5 | 2015-08-03 14:57:21 -0400 | [diff] [blame] | 276 | ``async`` and ``await`` are not recommended to be used as variable, class, |
| 277 | function or module names. Introduced by :pep:`492` in Python 3.5, they will |
| 278 | become proper keywords in Python 3.7. |
Yury Selivanov | 7a21911 | 2015-05-28 17:10:29 -0400 | [diff] [blame] | 279 | |
| 280 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 281 | Deprecated Python modules, functions and methods |
| 282 | ------------------------------------------------ |
| 283 | |
Brett Cannon | eae3079 | 2015-12-28 17:55:27 -0800 | [diff] [blame] | 284 | * :meth:`importlib.machinery.SourceFileLoader` and |
| 285 | :meth:`importlib.machinery.SourcelessFileLoader` are now deprecated. They |
| 286 | were the only remaining implementations of |
| 287 | :meth:`importlib.abc.Loader.load_module` in :mod:`importlib` that had not |
| 288 | been deprecated in previous versions of Python in favour of |
| 289 | :meth:`importlib.abc.Loader.exec_module`. |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 290 | |
| 291 | |
| 292 | Deprecated functions and types of the C API |
| 293 | ------------------------------------------- |
| 294 | |
| 295 | * None yet. |
| 296 | |
| 297 | |
| 298 | Deprecated features |
| 299 | ------------------- |
| 300 | |
Brett Cannon | 9b63868 | 2015-10-16 15:14:27 -0700 | [diff] [blame] | 301 | * The ``pyvenv`` script has been deprecated in favour of ``python3 -m venv``. |
| 302 | This prevents confusion as to what Python interpreter ``pyvenv`` is |
| 303 | connected to and thus what Python interpreter will be used by the virtual |
Brett Cannon | 63b8505 | 2016-01-15 13:33:03 -0800 | [diff] [blame] | 304 | environment. (Contributed by Brett Cannon in :issue:`25154`.) |
| 305 | |
| 306 | * When performing a relative import, falling back on ``__name__`` and |
| 307 | ``__path__`` from the calling module when ``__spec__`` or |
| 308 | ``__package__`` are not defined now raises an :exc:`ImportWarning`. |
| 309 | (Contributed by Rose Ames in :issue:`25791`.) |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 310 | |
| 311 | |
Martin Panter | 7e3a91a | 2016-02-10 04:40:48 +0000 | [diff] [blame] | 312 | Deprecated Python behavior |
| 313 | -------------------------- |
| 314 | |
| 315 | * Raising the :exc:`StopIteration` exception inside a generator will now generate a |
| 316 | :exc:`DeprecationWarning`, and will trigger a :exc:`RuntimeError` in Python 3.7. |
| 317 | See :ref:`whatsnew-pep-479` for details. |
| 318 | |
| 319 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 320 | Removed |
| 321 | ======= |
| 322 | |
| 323 | API and Feature Removals |
| 324 | ------------------------ |
| 325 | |
Yury Selivanov | 5661316 | 2015-07-23 17:51:34 +0300 | [diff] [blame] | 326 | * ``inspect.getmoduleinfo()`` was removed (was deprecated since CPython 3.3). |
Yury Selivanov | 6dfbc5d | 2015-07-23 17:49:00 +0300 | [diff] [blame] | 327 | :func:`inspect.getmodulename` should be used for obtaining the module |
| 328 | name for a given path. |
| 329 | |
Senthil Kumaran | 613065b | 2016-01-17 20:12:16 -0800 | [diff] [blame] | 330 | * ``traceback.Ignore`` class and ``traceback.usage``, ``traceback.modname``, |
| 331 | ``traceback.fullmodname``, ``traceback.find_lines_from_code``, |
| 332 | ``traceback.find_lines``, ``traceback.find_strings``, |
| 333 | ``traceback.find_executable_lines`` methods were removed from the |
| 334 | :mod:`traceback` module. They were undocumented methods deprecated since |
| 335 | Python 3.2 and equivalent functionality is available from private methods. |
| 336 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 337 | |
| 338 | Porting to Python 3.6 |
| 339 | ===================== |
| 340 | |
| 341 | This section lists previously described changes and other bugfixes |
| 342 | that may require changes to your code. |
| 343 | |
| 344 | Changes in the Python API |
| 345 | ------------------------- |
| 346 | |
Victor Stinner | f3914eb | 2016-01-20 12:16:21 +0100 | [diff] [blame] | 347 | * The format of the ``co_lnotab`` attribute of code objects changed to support |
| 348 | negative line number delta. By default, Python does not emit bytecode with |
| 349 | negative line number delta. Functions using ``frame.f_lineno``, |
| 350 | ``PyFrame_GetLineNumber()`` or ``PyCode_Addr2Line()`` are not affected. |
| 351 | Functions decoding directly ``co_lnotab`` should be updated to use a signed |
| 352 | 8-bit integer type for the line number delta, but it's only required to |
| 353 | support applications using negative line number delta. See |
| 354 | ``Objects/lnotab_notes.txt`` for the ``co_lnotab`` format and how to decode |
| 355 | it, and see the :pep:`511` for the rationale. |
| 356 | |
Brett Cannon | 1e3c3e9 | 2015-12-27 13:17:04 -0800 | [diff] [blame] | 357 | * The functions in the :mod:`compileall` module now return booleans instead |
| 358 | of ``1`` or ``0`` to represent success or failure, respectively. Thanks to |
| 359 | booleans being a subclass of integers, this should only be an issue if you |
| 360 | were doing identity checks for ``1`` or ``0``. See :issue:`25768`. |
| 361 | |
Robert Collins | dfa95c9 | 2015-08-10 09:53:30 +1200 | [diff] [blame] | 362 | * Reading the :attr:`~urllib.parse.SplitResult.port` attribute of |
| 363 | :func:`urllib.parse.urlsplit` and :func:`~urllib.parse.urlparse` results |
| 364 | now raises :exc:`ValueError` for out-of-range values, rather than |
| 365 | returning :const:`None`. See :issue:`20059`. |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 366 | |
Brett Cannon | c0d91af | 2015-10-16 12:21:37 -0700 | [diff] [blame] | 367 | * The :mod:`imp` module now raises a :exc:`DeprecationWarning` instead of |
| 368 | :exc:`PendingDeprecationWarning`. |
| 369 | |
Martin Panter | 28a465c | 2015-11-14 12:52:08 +0000 | [diff] [blame] | 370 | * The following modules have had missing APIs added to their :attr:`__all__` |
Martin Panter | e8afd01 | 2016-01-16 07:01:46 +0000 | [diff] [blame] | 371 | attributes to match the documented APIs: :mod:`calendar`, :mod:`csv`, |
| 372 | :mod:`enum`, :mod:`fileinput`, :mod:`ftplib`, :mod:`logging`, |
| 373 | :mod:`optparse`, :mod:`tarfile`, :mod:`threading` and |
Martin Panter | 28a465c | 2015-11-14 12:52:08 +0000 | [diff] [blame] | 374 | :mod:`wave`. This means they will export new symbols when ``import *`` |
| 375 | is used. See :issue:`23883`. |
| 376 | |
Brett Cannon | 849113a | 2016-01-22 15:25:50 -0800 | [diff] [blame] | 377 | * When performing a relative import, if ``__package__`` does not compare equal |
| 378 | to ``__spec__.parent`` then :exc:`ImportWarning` is raised. |
| 379 | (Contributed by Brett Cannon in :issue:`25791`.) |
Brett Cannon | 63b8505 | 2016-01-15 13:33:03 -0800 | [diff] [blame] | 380 | |
Brett Cannon | 9fa8126 | 2016-01-22 16:39:02 -0800 | [diff] [blame] | 381 | * When a relative import is performed and no parent package is known, then |
| 382 | :exc:`ImportError` will be raised. Previously, :exc:`SystemError` could be |
Martin Panter | d9108d1 | 2016-02-21 08:49:56 +0000 | [diff] [blame] | 383 | raised. (Contributed by Brett Cannon in :issue:`18018`.) |
| 384 | |
| 385 | * Servers based on the :mod:`socketserver` module, including those |
| 386 | defined in :mod:`http.server`, :mod:`xmlrpc.server` and |
| 387 | :mod:`wsgiref.simple_server`, now only catch exceptions derived |
| 388 | from :exc:`Exception`. Therefore if a request handler raises |
| 389 | an exception like :exc:`SystemExit` or :exc:`KeyboardInterrupt`, |
| 390 | :meth:`~socketserver.BaseServer.handle_error` is no longer called, and |
| 391 | the exception will stop a single-threaded server. (Contributed by |
| 392 | Martin Panter in :issue:`23430`.) |
Brett Cannon | 9fa8126 | 2016-01-22 16:39:02 -0800 | [diff] [blame] | 393 | |
Yury Selivanov | d1da507 | 2015-05-27 22:09:10 -0400 | [diff] [blame] | 394 | |
| 395 | Changes in the C API |
| 396 | -------------------- |
| 397 | |
Martin Panter | b4ce1fc | 2015-11-30 03:18:29 +0000 | [diff] [blame] | 398 | * :c:func:`Py_Exit` (and the main interpreter) now override the exit status |
| 399 | with 120 if flushing buffered data failed. See :issue:`5319`. |