|
40 | 40 | * Credit the author of a patch or bugfix. Just the name is |
41 | 41 | sufficient; the e-mail address isn't necessary. |
42 | 42 | |
43 | | - * It's helpful to add the bug/patch number in an parenthetical |
| 43 | + * It's helpful to add the bug/patch number in a parenthetical comment. |
44 | 44 | |
45 | 45 | XXX Describe the transmogrify() function added to the socket |
46 | 46 | module. |
47 | 47 | (Contributed by P.Y. Developer; :issue:`12345`.) |
48 | 48 | |
49 | | - This saves the maintainer the effort of going through the SVN logs |
| 49 | + This saves the maintainer some effort going through the SVN logs |
50 | 50 | when researching a change. |
51 | 51 |
|
52 | | -This article explains the new features in Python 2.6. No release date for |
53 | | -Python 2.6 has been set; it will probably be released in mid 2008. |
| 52 | +This article explains the new features in Python 2.6. The release |
| 53 | +schedule is described in :pep:`361`; currently the final release is |
| 54 | +scheduled for September 3 2008. |
54 | 55 |
|
55 | 56 | This article doesn't attempt to provide a complete specification of |
56 | 57 | the new features, but instead provides a convenient overview. For |
57 | 58 | full details, you should refer to the documentation for Python 2.6. If |
58 | | -you want to understand the complete implementation and design |
59 | | -rationale, refer to the PEP for a particular new feature. For smaller |
60 | | -changes, this edition of "What's New in Python" links to the bug/patch |
61 | | -item for each change whenever possible. |
| 59 | +you want to understand the rationale for the design and |
| 60 | +implementation, refer to the PEP for a particular new feature. |
| 61 | +Whenever possible, "What's New in Python" links to the bug/patch item |
| 62 | +for each change. |
62 | 63 |
|
63 | 64 | .. Compare with previous release in 2 - 3 sentences here. |
64 | 65 | add hyperlink when the documentation becomes available online. |
@@ -481,24 +482,41 @@ can now be used in scripts running from inside a package. |
481 | 482 |
|
482 | 483 | .. ====================================================================== |
483 | 484 |
|
484 | | -.. :: |
| 485 | +.. _pep-0370: |
485 | 486 |
|
486 | | - .. _pep-0370: |
| 487 | +PEP 370: Per-user ``site-packages`` Directory |
| 488 | +===================================================== |
| 489 | + |
| 490 | +When you run Python, the module search path ``sys.modules`` usually |
| 491 | +includes a directory whose path ends in ``"site-packages"``. This |
| 492 | +directory is intended to hold locally-installed packages available to |
| 493 | +all users on a machine or using a particular site installation. |
| 494 | + |
| 495 | +Python 2.6 introduces a convention for user-specific site directories. |
| 496 | +The directory varies depending on the platform: |
| 497 | + |
| 498 | +* Unix and MacOS: :file:`~/.local/` |
| 499 | +* Windows: :file:`%APPDATA%/Python` |
487 | 500 |
|
488 | | - PEP 370: XXX |
489 | | - ===================================================== |
| 501 | +Within this directory, there will be version-specific subdirectories, |
| 502 | +such as :file:`lib/python2.6/site-packages` on Unix/MacOS and |
| 503 | +:file:`Python26/site-packages` on Windows. |
490 | 504 |
|
491 | | - When you run Python, the module search page ``sys.modules`` usually |
492 | | - includes a directory whose path ends in ``"site-packages"``. This |
493 | | - directory is intended to hold locally-installed packages available to |
494 | | - all users on a machine or using a particular site installation. |
| 505 | +If you don't like the default directory, it can be overridden by an |
| 506 | +environment variable. :envvar:`PYTHONUSERBASE` sets the root |
| 507 | +directory used for all Python versions supporting this feature. On |
| 508 | +Windows, the directory for application-specific data can be changed by |
| 509 | +setting the :envvar:`APPDATA` environment variable. You can also |
| 510 | +modify the :file:`site.py` file for your Python installation. |
495 | 511 |
|
496 | | - Python 2.6 introduces a convention for user-specific site directories. |
| 512 | +The feature can be disabled entirely by running Python with the |
| 513 | +:option:`-s` option or setting the :envvar:`PYTHONNOUSERSITE` |
| 514 | +environment variable. |
497 | 515 |
|
498 | | - .. seealso:: |
| 516 | +.. seealso:: |
499 | 517 |
|
500 | | - :pep:`370` - XXX |
501 | | - PEP written by XXX; implemented by Christian Heimes. |
| 518 | + :pep:`370` - Per-user ``site-packages`` Directory |
| 519 | + PEP written and implemented by Christian Heimes. |
502 | 520 |
|
503 | 521 |
|
504 | 522 | .. ====================================================================== |
@@ -1450,6 +1468,12 @@ fixes. Here's a partial list of the most notable changes, sorted alphabetically |
1450 | 1468 | by module name. Consult the :file:`Misc/NEWS` file in the source tree for a more |
1451 | 1469 | complete list of changes, or look through the CVS logs for all the details. |
1452 | 1470 |
|
| 1471 | +* (3.0-warning mode) The :mod:`audiodev` module is being deprecated, |
| 1472 | + and has been removed from Python 3.0, so importing it now triggers a |
| 1473 | + warning. The module hasn't been maintained for several versions, |
| 1474 | + and is written against an outdated sound interface for SunOS and |
| 1475 | + IRIX. |
| 1476 | + |
1453 | 1477 | * The :mod:`bsddb.dbshelve` module now uses the highest pickling protocol |
1454 | 1478 | available, instead of restricting itself to protocol 1. |
1455 | 1479 | (Contributed by W. Barnes; :issue:`1551443`.) |
@@ -2104,7 +2128,12 @@ complete list of changes, or look through the CVS logs for all the details. |
2104 | 2128 |
|
2105 | 2129 | (Added by Facundo Batista.) |
2106 | 2130 |
|
2107 | | -* The XML-RPC classes :class:`SimpleXMLRPCServer` and :class:`DocXMLRPCServer` |
| 2131 | +* The :mod:`warnings` module's :func:`formatwarning` and :func:`showwarning` |
| 2132 | + gained an optional *line* argument that can be used to supply the |
| 2133 | + line of source code. (Added as part of :issue:`1631171`, which re-implemented |
| 2134 | + part of the :mod:`warnings` module in C code.) |
| 2135 | + |
| 2136 | +* The XML-RPC :class:`SimpleXMLRPCServer` and :class:`DocXMLRPCServer` |
2108 | 2137 | classes can now be prevented from immediately opening and binding to |
2109 | 2138 | their socket by passing True as the ``bind_and_activate`` |
2110 | 2139 | constructor parameter. This can be used to modify the instance's |
@@ -2144,6 +2173,9 @@ complete list of changes, or look through the CVS logs for all the details. |
2144 | 2173 |
|
2145 | 2174 | (Contributed by Alan McIntyre; :issue:`467924`.) |
2146 | 2175 |
|
| 2176 | + Also, :mod:`zipfile` now supports using Unicode filenames |
| 2177 | + for archived files. (Contributed by Alexey Borzenkov; :issue:`1734346`.) |
| 2178 | + |
2147 | 2179 | .. ====================================================================== |
2148 | 2180 | .. whole new modules get described in subsections here |
2149 | 2181 |
|
|
0 commit comments