# SOME DESCRIPTIVE TITLE.

# Copyright (C) 2001-2022, Python Software Foundation

# This file is distributed under the same license as the Python package.

#

# Translators:

msgid ""

msgstr ""

"Project-Id-Version: Python 3.12\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2023-08-23 00:03+0000\n"

"PO-Revision-Date: 2018-05-23 16:20+0000\n"

"Last-Translator: Adrian Liaw <adrianliaw2000@gmail.com>\n"

"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"

"tw)\n"

"Language: zh_TW\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../whatsnew/3.2.rst:3

msgid "What's New In Python 3.2"

msgstr "Python 3.2 有什麼新功能"

#: ../../whatsnew/3.2.rst:0

msgid "Author"

msgstr "作者"

#: ../../whatsnew/3.2.rst:5

msgid "Raymond Hettinger"

msgstr "Raymond Hettinger"

#: ../../whatsnew/3.2.rst:51

msgid ""

"This article explains the new features in Python 3.2 as compared to 3.1. "

"Python 3.2 was released on February 20, 2011. It focuses on a few highlights "

"and gives a few examples. For full details, see the `Misc/NEWS <https://"

"github.com/python/cpython/blob/076ca6c3c8df3030307e548d9be792ce3c1c6eea/Misc/"

"NEWS>`__ file."

msgstr ""

#: ../../whatsnew/3.2.rst:60

msgid ":pep:`392` - Python 3.2 Release Schedule"

msgstr ""

#: ../../whatsnew/3.2.rst:64

msgid "PEP 384: Defining a Stable ABI"

msgstr ""

#: ../../whatsnew/3.2.rst:66

msgid ""

"In the past, extension modules built for one Python version were often not "

"usable with other Python versions. Particularly on Windows, every feature "

"release of Python required rebuilding all extension modules that one wanted "

"to use. This requirement was the result of the free access to Python "

"interpreter internals that extension modules could use."

msgstr ""

#: ../../whatsnew/3.2.rst:72

msgid ""

"With Python 3.2, an alternative approach becomes available: extension "

"modules which restrict themselves to a limited API (by defining "

"Py_LIMITED_API) cannot use many of the internals, but are constrained to a "

"set of API functions that are promised to be stable for several releases. As "

"a consequence, extension modules built for 3.2 in that mode will also work "

"with 3.3, 3.4, and so on. Extension modules that make use of details of "

"memory structures can still be built, but will need to be recompiled for "

"every feature release."

msgstr ""

#: ../../whatsnew/3.2.rst:83

msgid ":pep:`384` - Defining a Stable ABI"

msgstr ""

#: ../../whatsnew/3.2.rst:84

msgid "PEP written by Martin von Löwis."

msgstr "由 Martin von Löwis 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:88

msgid "PEP 389: Argparse Command Line Parsing Module"

msgstr ""

#: ../../whatsnew/3.2.rst:90

msgid ""

"A new module for command line parsing, :mod:`argparse`, was introduced to "

"overcome the limitations of :mod:`optparse` which did not provide support "

"for positional arguments (not just options), subcommands, required options "

"and other common patterns of specifying and validating options."

msgstr ""

#: ../../whatsnew/3.2.rst:95

msgid ""

"This module has already had widespread success in the community as a third-"

"party module. Being more fully featured than its predecessor, the :mod:"

"`argparse` module is now the preferred module for command-line processing. "

"The older module is still being kept available because of the substantial "

"amount of legacy code that depends on it."

msgstr ""

#: ../../whatsnew/3.2.rst:101

msgid ""

"Here's an annotated example parser showing features like limiting results to "

"a set of choices, specifying a *metavar* in the help screen, validating that "

"one or more positional arguments is present, and making a required option::"

msgstr ""

#: ../../whatsnew/3.2.rst:120

msgid "Example of calling the parser on a command string::"

msgstr ""

#: ../../whatsnew/3.2.rst:131

msgid "Example of the parser's automatically generated help::"

msgstr ""

#: ../../whatsnew/3.2.rst:150

msgid ""

"An especially nice :mod:`argparse` feature is the ability to define "

"subparsers, each with their own argument patterns and help displays::"

msgstr ""

#: ../../whatsnew/3.2.rst:176

msgid ":pep:`389` - New Command Line Parsing Module"

msgstr ""

#: ../../whatsnew/3.2.rst:176

msgid "PEP written by Steven Bethard."

msgstr "由 Steven Bethard 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:178

msgid ""

":ref:`upgrading-optparse-code` for details on the differences from :mod:"

"`optparse`."

msgstr ""

#: ../../whatsnew/3.2.rst:182

msgid "PEP 391: Dictionary Based Configuration for Logging"

msgstr ""

#: ../../whatsnew/3.2.rst:184

msgid ""

"The :mod:`logging` module provided two kinds of configuration, one style "

"with function calls for each option or another style driven by an external "

"file saved in a :mod:`ConfigParser` format. Those options did not provide "

"the flexibility to create configurations from JSON or YAML files, nor did "

"they support incremental configuration, which is needed for specifying "

"logger options from a command line."

msgstr ""

#: ../../whatsnew/3.2.rst:191

msgid ""

"To support a more flexible style, the module now offers :func:`logging."

"config.dictConfig` for specifying logging configuration with plain Python "

"dictionaries. The configuration options include formatters, handlers, "

"filters, and loggers. Here's a working example of a configuration "

"dictionary::"

msgstr ""

#: ../../whatsnew/3.2.rst:215

msgid ""

"If that dictionary is stored in a file called :file:`conf.json`, it can be "

"loaded and called with code like this::"

msgstr ""

#: ../../whatsnew/3.2.rst:230

msgid ":pep:`391` - Dictionary Based Configuration for Logging"

msgstr ""

#: ../../whatsnew/3.2.rst:231

msgid "PEP written by Vinay Sajip."

msgstr "由 Vinay Sajip 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:235

msgid "PEP 3148: The ``concurrent.futures`` module"

msgstr ""

#: ../../whatsnew/3.2.rst:237

msgid ""

"Code for creating and managing concurrency is being collected in a new top-"

"level namespace, *concurrent*. Its first member is a *futures* package "

"which provides a uniform high-level interface for managing threads and "

"processes."

msgstr ""

#: ../../whatsnew/3.2.rst:241

msgid ""

"The design for :mod:`concurrent.futures` was inspired by the *java.util."

"concurrent* package. In that model, a running call and its result are "

"represented by a :class:`~concurrent.futures.Future` object that abstracts "

"features common to threads, processes, and remote procedure calls. That "

"object supports status checks (running or done), timeouts, cancellations, "

"adding callbacks, and access to results or exceptions."

msgstr ""

#: ../../whatsnew/3.2.rst:248

msgid ""

"The primary offering of the new module is a pair of executor classes for "

"launching and managing calls. The goal of the executors is to make it "

"easier to use existing tools for making parallel calls. They save the effort "

"needed to setup a pool of resources, launch the calls, create a results "

"queue, add time-out handling, and limit the total number of threads, "

"processes, or remote procedure calls."

msgstr ""

#: ../../whatsnew/3.2.rst:255

msgid ""

"Ideally, each application should share a single executor across multiple "

"components so that process and thread limits can be centrally managed. This "

"solves the design challenge that arises when each component has its own "

"competing strategy for resource management."

msgstr ""

#: ../../whatsnew/3.2.rst:260

msgid ""

"Both classes share a common interface with three methods: :meth:`~concurrent."

"futures.Executor.submit` for scheduling a callable and returning a :class:"

"`~concurrent.futures.Future` object; :meth:`~concurrent.futures.Executor."

"map` for scheduling many asynchronous calls at a time, and :meth:"

"`~concurrent.futures.Executor.shutdown` for freeing resources. The class is "

"a :term:`context manager` and can be used in a :keyword:`with` statement to "

"assure that resources are automatically released when currently pending "

"futures are done executing."

msgstr ""

#: ../../whatsnew/3.2.rst:269

msgid ""

"A simple of example of :class:`~concurrent.futures.ThreadPoolExecutor` is a "

"launch of four parallel threads for copying files::"

msgstr ""

#: ../../whatsnew/3.2.rst:282

msgid ":pep:`3148` - Futures -- Execute Computations Asynchronously"

msgstr ""

#: ../../whatsnew/3.2.rst:282

msgid "PEP written by Brian Quinlan."

msgstr "由 Brian Quinlan 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:284

msgid ""

":ref:`Code for Threaded Parallel URL reads<threadpoolexecutor-example>`, an "

"example using threads to fetch multiple web pages in parallel."

msgstr ""

#: ../../whatsnew/3.2.rst:287

msgid ""

":ref:`Code for computing prime numbers in parallel<processpoolexecutor-"

"example>`, an example demonstrating :class:`~concurrent.futures."

"ProcessPoolExecutor`."

msgstr ""

#: ../../whatsnew/3.2.rst:293

msgid "PEP 3147: PYC Repository Directories"

msgstr ""

#: ../../whatsnew/3.2.rst:295

msgid ""

"Python's scheme for caching bytecode in *.pyc* files did not work well in "

"environments with multiple Python interpreters. If one interpreter "

"encountered a cached file created by another interpreter, it would recompile "

"the source and overwrite the cached file, thus losing the benefits of "

"caching."

msgstr ""

#: ../../whatsnew/3.2.rst:300

msgid ""

"The issue of \"pyc fights\" has become more pronounced as it has become "

"commonplace for Linux distributions to ship with multiple versions of "

"Python. These conflicts also arise with CPython alternatives such as Unladen "

"Swallow."

msgstr ""

#: ../../whatsnew/3.2.rst:304

msgid ""

"To solve this problem, Python's import machinery has been extended to use "

"distinct filenames for each interpreter. Instead of Python 3.2 and Python "

"3.3 and Unladen Swallow each competing for a file called \"mymodule.pyc\", "

"they will now look for \"mymodule.cpython-32.pyc\", \"mymodule.cpython-33."

"pyc\", and \"mymodule.unladen10.pyc\". And to prevent all of these new "

"files from cluttering source directories, the *pyc* files are now collected "

"in a \"__pycache__\" directory stored under the package directory."

msgstr ""

#: ../../whatsnew/3.2.rst:312

msgid ""

"Aside from the filenames and target directories, the new scheme has a few "

"aspects that are visible to the programmer:"

msgstr ""

#: ../../whatsnew/3.2.rst:315

msgid ""

"Imported modules now have a :attr:`__cached__` attribute which stores the "

"name of the actual file that was imported:"

msgstr ""

#: ../../whatsnew/3.2.rst:322

msgid ""

"The tag that is unique to each interpreter is accessible from the :mod:`!"

"imp` module:"

msgstr ""

#: ../../whatsnew/3.2.rst:329

msgid ""

"Scripts that try to deduce source filename from the imported file now need "

"to be smarter. It is no longer sufficient to simply strip the \"c\" from a "

"\".pyc\" filename. Instead, use the new functions in the :mod:`!imp` module:"

msgstr ""

#: ../../whatsnew/3.2.rst:338

msgid ""

"The :mod:`py_compile` and :mod:`compileall` modules have been updated to "

"reflect the new naming convention and target directory. The command-line "

"invocation of *compileall* has new options: ``-i`` for specifying a list of "

"files and directories to compile and ``-b`` which causes bytecode files to "

"be written to their legacy location rather than *__pycache__*."

msgstr ""

#: ../../whatsnew/3.2.rst:345

msgid ""

"The :mod:`importlib.abc` module has been updated with new :term:`abstract "

"base classes <abstract base class>` for loading bytecode files. The "

"obsolete ABCs, :class:`~importlib.abc.PyLoader` and :class:`~importlib.abc."

"PyPycLoader`, have been deprecated (instructions on how to stay Python 3.1 "

"compatible are included with the documentation)."

msgstr ""

#: ../../whatsnew/3.2.rst:353

msgid ":pep:`3147` - PYC Repository Directories"

msgstr ""

#: ../../whatsnew/3.2.rst:354 ../../whatsnew/3.2.rst:385

msgid "PEP written by Barry Warsaw."

msgstr "由 Barry Warsaw 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:358

msgid "PEP 3149: ABI Version Tagged .so Files"

msgstr ""

#: ../../whatsnew/3.2.rst:360

msgid ""

"The PYC repository directory allows multiple bytecode cache files to be co-"

"located. This PEP implements a similar mechanism for shared object files by "

"giving them a common directory and distinct names for each version."

msgstr ""

#: ../../whatsnew/3.2.rst:364

msgid ""

"The common directory is \"pyshared\" and the file names are made distinct by "

"identifying the Python implementation (such as CPython, PyPy, Jython, etc.), "

"the major and minor version numbers, and optional build flags (such as \"d\" "

"for debug, \"m\" for pymalloc, \"u\" for wide-unicode). For an arbitrary "

"package \"foo\", you may see these files when the distribution package is "

"installed::"

msgstr ""

#: ../../whatsnew/3.2.rst:373

msgid ""

"In Python itself, the tags are accessible from functions in the :mod:"

"`sysconfig` module::"

msgstr ""

#: ../../whatsnew/3.2.rst:384

msgid ":pep:`3149` - ABI Version Tagged .so Files"

msgstr ""

#: ../../whatsnew/3.2.rst:389

msgid "PEP 3333: Python Web Server Gateway Interface v1.0.1"

msgstr ""

#: ../../whatsnew/3.2.rst:391

msgid ""

"This informational PEP clarifies how bytes/text issues are to be handled by "

"the WSGI protocol. The challenge is that string handling in Python 3 is "

"most conveniently handled with the :class:`str` type even though the HTTP "

"protocol is itself bytes oriented."

msgstr ""

#: ../../whatsnew/3.2.rst:396

msgid ""

"The PEP differentiates so-called *native strings* that are used for request/"

"response headers and metadata versus *byte strings* which are used for the "

"bodies of requests and responses."

msgstr ""

#: ../../whatsnew/3.2.rst:400

msgid ""

"The *native strings* are always of type :class:`str` but are restricted to "

"code points between *U+0000* through *U+00FF* which are translatable to "

"bytes using *Latin-1* encoding. These strings are used for the keys and "

"values in the environment dictionary and for response headers and statuses "

"in the :func:`start_response` function. They must follow :rfc:`2616` with "

"respect to encoding. That is, they must either be *ISO-8859-1* characters or "

"use :rfc:`2047` MIME encoding."

msgstr ""

#: ../../whatsnew/3.2.rst:408

msgid ""

"For developers porting WSGI applications from Python 2, here are the salient "

"points:"

msgstr ""

#: ../../whatsnew/3.2.rst:411

msgid ""

"If the app already used strings for headers in Python 2, no change is needed."

msgstr ""

#: ../../whatsnew/3.2.rst:413

msgid ""

"If instead, the app encoded output headers or decoded input headers, then "

"the headers will need to be re-encoded to Latin-1. For example, an output "

"header encoded in utf-8 was using ``h.encode('utf-8')`` now needs to convert "

"from bytes to native strings using ``h.encode('utf-8').decode('latin-1')``."

msgstr ""

#: ../../whatsnew/3.2.rst:418

msgid ""

"Values yielded by an application or sent using the :meth:`write` method must "

"be byte strings. The :func:`start_response` function and environ must use "

"native strings. The two cannot be mixed."

msgstr ""

#: ../../whatsnew/3.2.rst:422

msgid ""

"For server implementers writing CGI-to-WSGI pathways or other CGI-style "

"protocols, the users must to be able access the environment using native "

"strings even though the underlying platform may have a different "

"convention. To bridge this gap, the :mod:`wsgiref` module has a new "

"function, :func:`wsgiref.handlers.read_environ` for transcoding CGI "

"variables from :data:`os.environ` into native strings and returning a new "

"dictionary."

msgstr ""

#: ../../whatsnew/3.2.rst:431

msgid ":pep:`3333` - Python Web Server Gateway Interface v1.0.1"

msgstr ""

#: ../../whatsnew/3.2.rst:432

msgid "PEP written by Phillip Eby."

msgstr "由 Phillip Eby 撰寫 PEP。"

#: ../../whatsnew/3.2.rst:436

msgid "Other Language Changes"

msgstr "其他語言更動"

#: ../../whatsnew/3.2.rst:438

msgid "Some smaller changes made to the core Python language are:"

msgstr ""

#: ../../whatsnew/3.2.rst:440

msgid ""

"String formatting for :func:`format` and :meth:`str.format` gained new "

"capabilities for the format character **#**. Previously, for integers in "

"binary, octal, or hexadecimal, it caused the output to be prefixed with "

"'0b', '0o', or '0x' respectively. Now it can also handle floats, complex, "

"and Decimal, causing the output to always have a decimal point even when no "

"digits follow it."

msgstr ""

#: ../../whatsnew/3.2.rst:452

msgid ""

"(Suggested by Mark Dickinson and implemented by Eric Smith in :issue:`7094`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:454

msgid ""

"There is also a new :meth:`str.format_map` method that extends the "

"capabilities of the existing :meth:`str.format` method by accepting "

"arbitrary :term:`mapping` objects. This new method makes it possible to use "

"string formatting with any of Python's many dictionary-like objects such as :"

"class:`~collections.defaultdict`, :class:`~shelve.Shelf`, :class:"

"`~configparser.ConfigParser`, or :mod:`dbm`. It is also useful with custom :"

"class:`dict` subclasses that normalize keys before look-up or that supply a :"

"meth:`__missing__` method for unknown keys::"

msgstr ""

#: ../../whatsnew/3.2.rst:483

msgid ""

"(Suggested by Raymond Hettinger and implemented by Eric Smith in :issue:"

"`6081`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:486

msgid ""

"The interpreter can now be started with a quiet option, ``-q``, to prevent "

"the copyright and version information from being displayed in the "

"interactive mode. The option can be introspected using the :data:`sys."

"flags` attribute:"

msgstr ""

#: ../../whatsnew/3.2.rst:498

msgid "(Contributed by Marcin Wojdyr in :issue:`1772833`)."

msgstr "（由 Marcin Wojdyr 在 :issue:`1772833` 中貢獻）。"

#: ../../whatsnew/3.2.rst:500

msgid ""

"The :func:`hasattr` function works by calling :func:`getattr` and detecting "

"whether an exception is raised. This technique allows it to detect methods "

"created dynamically by :meth:`__getattr__` or :meth:`__getattribute__` which "

"would otherwise be absent from the class dictionary. Formerly, *hasattr* "

"would catch any exception, possibly masking genuine errors. Now, *hasattr* "

"has been tightened to only catch :exc:`AttributeError` and let other "

"exceptions pass through::"

msgstr ""

#: ../../whatsnew/3.2.rst:519

msgid ""

"(Discovered by Yury Selivanov and fixed by Benjamin Peterson; :issue:`9666`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:521

msgid ""

"The :func:`str` of a float or complex number is now the same as its :func:"

"`repr`. Previously, the :func:`str` form was shorter but that just caused "

"confusion and is no longer needed now that the shortest possible :func:"

"`repr` is displayed by default:"

msgstr ""

#: ../../whatsnew/3.2.rst:532

msgid "(Proposed and implemented by Mark Dickinson; :issue:`9337`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:534

msgid ""

":class:`memoryview` objects now have a :meth:`~memoryview.release()` method "

"and they also now support the context management protocol. This allows "

"timely release of any resources that were acquired when requesting a buffer "

"from the original object."

msgstr ""

#: ../../whatsnew/3.2.rst:543

msgid "(Added by Antoine Pitrou; :issue:`9757`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:545

msgid ""

"Previously it was illegal to delete a name from the local namespace if it "

"occurs as a free variable in a nested block::"

msgstr ""

#: ../../whatsnew/3.2.rst:554

msgid ""

"This is now allowed. Remember that the target of an :keyword:`except` "

"clause is cleared, so this code which used to work with Python 2.6, raised "

"a :exc:`SyntaxError` with Python 3.1 and now works again::"

msgstr ""

#: ../../whatsnew/3.2.rst:567

msgid "(See :issue:`4617`.)"

msgstr "（請見 :issue:`4617`\\ 。）"

#: ../../whatsnew/3.2.rst:569

msgid ""

":ref:`Struct sequence types <struct-sequence-objects>` are now subclasses of "

"tuple. This means that C structures like those returned by :func:`os.stat`, :"

"func:`time.gmtime`, and :data:`sys.version_info` now work like a :term:"

"`named tuple` and now work with functions and methods that expect a tuple as "

"an argument. This is a big step forward in making the C structures as "

"flexible as their pure Python counterparts:"

msgstr ""

#: ../../whatsnew/3.2.rst:582

msgid ""

"(Suggested by Arfrever Frehtes Taifersar Arahesis and implemented by "

"Benjamin Peterson in :issue:`8413`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:585

msgid ""

"Warnings are now easier to control using the :envvar:`PYTHONWARNINGS` "

"environment variable as an alternative to using ``-W`` at the command line:"

msgstr ""

#: ../../whatsnew/3.2.rst:592

msgid ""

"(Suggested by Barry Warsaw and implemented by Philip Jenvey in :issue:"

"`7301`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:594

msgid ""

"A new warning category, :exc:`ResourceWarning`, has been added. It is "

"emitted when potential issues with resource consumption or cleanup are "

"detected. It is silenced by default in normal release builds but can be "

"enabled through the means provided by the :mod:`warnings` module, or on the "

"command line."

msgstr ""

#: ../../whatsnew/3.2.rst:600

msgid ""

"A :exc:`ResourceWarning` is issued at interpreter shutdown if the :data:`gc."

"garbage` list isn't empty, and if :const:`gc.DEBUG_UNCOLLECTABLE` is set, "

"all uncollectable objects are printed. This is meant to make the programmer "

"aware that their code contains object finalization issues."

msgstr ""

#: ../../whatsnew/3.2.rst:605

msgid ""

"A :exc:`ResourceWarning` is also issued when a :term:`file object` is "

"destroyed without having been explicitly closed. While the deallocator for "

"such object ensures it closes the underlying operating system resource "

"(usually, a file descriptor), the delay in deallocating the object could "

"produce various issues, especially under Windows. Here is an example of "

"enabling the warning from the command line:"

msgstr ""

#: ../../whatsnew/3.2.rst:619

msgid ""

"(Added by Antoine Pitrou and Georg Brandl in :issue:`10093` and :issue:"

"`477863`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:621

msgid ""

":class:`range` objects now support *index* and *count* methods. This is part "

"of an effort to make more objects fully implement the :class:`collections."

"Sequence` :term:`abstract base class`. As a result, the language will have "

"a more uniform API. In addition, :class:`range` objects now support slicing "

"and negative indices, even with values larger than :data:`sys.maxsize`. "

"This makes *range* more interoperable with lists::"

msgstr ""

#: ../../whatsnew/3.2.rst:637

msgid ""

"(Contributed by Daniel Stutzbach in :issue:`9213`, by Alexander Belopolsky "

"in :issue:`2690`, and by Nick Coghlan in :issue:`10889`.)"

msgstr ""

"（由 Daniel Stutzbach 在 :issue:`9213`、Alexander Belopolsky 在 :issue:"

"`2690`、Nick Coghlan 在 :issue:`10889` 中貢獻。）"

#: ../../whatsnew/3.2.rst:640

msgid ""

"The :func:`callable` builtin function from Py2.x was resurrected. It "

"provides a concise, readable alternative to using an :term:`abstract base "

"class` in an expression like ``isinstance(x, collections.Callable)``:"

msgstr ""

#: ../../whatsnew/3.2.rst:649

msgid "(See :issue:`10518`.)"

msgstr "（請見 :issue:`10518`\\ 。）"

#: ../../whatsnew/3.2.rst:651

msgid ""

"Python's import mechanism can now load modules installed in directories with "

"non-ASCII characters in the path name. This solved an aggravating problem "

"with home directories for users with non-ASCII characters in their usernames."

msgstr ""

#: ../../whatsnew/3.2.rst:655

msgid "(Required extensive work by Victor Stinner in :issue:`9425`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:659

msgid "New, Improved, and Deprecated Modules"

msgstr ""

#: ../../whatsnew/3.2.rst:661

msgid ""

"Python's standard library has undergone significant maintenance efforts and "

"quality improvements."

msgstr ""

#: ../../whatsnew/3.2.rst:664

msgid ""

"The biggest news for Python 3.2 is that the :mod:`email` package, :mod:"

"`mailbox` module, and :mod:`nntplib` modules now work correctly with the "

"bytes/text model in Python 3. For the first time, there is correct handling "

"of messages with mixed encodings."

msgstr ""

#: ../../whatsnew/3.2.rst:669

msgid ""

"Throughout the standard library, there has been more careful attention to "

"encodings and text versus bytes issues. In particular, interactions with "

"the operating system are now better able to exchange non-ASCII data using "

"the Windows MBCS encoding, locale-aware encodings, or UTF-8."

msgstr ""

#: ../../whatsnew/3.2.rst:674

msgid ""

"Another significant win is the addition of substantially better support for "

"*SSL* connections and security certificates."

msgstr ""

#: ../../whatsnew/3.2.rst:677

msgid ""

"In addition, more classes now implement a :term:`context manager` to support "

"convenient and reliable resource clean-up using a :keyword:`with` statement."

msgstr ""

#: ../../whatsnew/3.2.rst:681

msgid "email"

msgstr "email"

#: ../../whatsnew/3.2.rst:683

msgid ""

"The usability of the :mod:`email` package in Python 3 has been mostly fixed "

"by the extensive efforts of R. David Murray. The problem was that emails "

"are typically read and stored in the form of :class:`bytes` rather than :"

"class:`str` text, and they may contain multiple encodings within a single "

"email. So, the email package had to be extended to parse and generate email "

"messages in bytes format."

msgstr ""

#: ../../whatsnew/3.2.rst:690

msgid ""

"New functions :func:`~email.message_from_bytes` and :func:`~email."

"message_from_binary_file`, and new classes :class:`~email.parser."

"BytesFeedParser` and :class:`~email.parser.BytesParser` allow binary message "

"data to be parsed into model objects."

msgstr ""

#: ../../whatsnew/3.2.rst:695

msgid ""

"Given bytes input to the model, :meth:`~email.message.Message.get_payload` "

"will by default decode a message body that has a :mailheader:`Content-"

"Transfer-Encoding` of *8bit* using the charset specified in the MIME headers "

"and return the resulting string."

msgstr ""

#: ../../whatsnew/3.2.rst:700

msgid ""

"Given bytes input to the model, :class:`~email.generator.Generator` will "

"convert message bodies that have a :mailheader:`Content-Transfer-Encoding` "

"of *8bit* to instead have a *7bit* :mailheader:`Content-Transfer-Encoding`."

msgstr ""

#: ../../whatsnew/3.2.rst:704

msgid ""

"Headers with unencoded non-ASCII bytes are deemed to be :rfc:`2047`\\ -"

"encoded using the *unknown-8bit* character set."

msgstr ""

#: ../../whatsnew/3.2.rst:707

msgid ""

"A new class :class:`~email.generator.BytesGenerator` produces bytes as "

"output, preserving any unchanged non-ASCII data that was present in the "

"input used to build the model, including message bodies with a :mailheader:"

"`Content-Transfer-Encoding` of *8bit*."

msgstr ""

#: ../../whatsnew/3.2.rst:712

msgid ""

"The :mod:`smtplib` :class:`~smtplib.SMTP` class now accepts a byte string "

"for the *msg* argument to the :meth:`~smtplib.SMTP.sendmail` method, and a "

"new method, :meth:`~smtplib.SMTP.send_message` accepts a :class:`~email."

"message.Message` object and can optionally obtain the *from_addr* and "

"*to_addrs* addresses directly from the object."

msgstr ""

#: ../../whatsnew/3.2.rst:718

msgid ""

"(Proposed and implemented by R. David Murray, :issue:`4661` and :issue:"

"`10321`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:721

msgid "elementtree"

msgstr "elementtree"

#: ../../whatsnew/3.2.rst:723

msgid ""

"The :mod:`xml.etree.ElementTree` package and its :mod:`xml.etree."

"cElementTree` counterpart have been updated to version 1.3."

msgstr ""

#: ../../whatsnew/3.2.rst:726

msgid "Several new and useful functions and methods have been added:"

msgstr ""

#: ../../whatsnew/3.2.rst:728

msgid ""

":func:`xml.etree.ElementTree.fromstringlist` which builds an XML document "

"from a sequence of fragments"

msgstr ""

#: ../../whatsnew/3.2.rst:730

msgid ""

":func:`xml.etree.ElementTree.register_namespace` for registering a global "

"namespace prefix"

msgstr ""

#: ../../whatsnew/3.2.rst:732

msgid ""

":func:`xml.etree.ElementTree.tostringlist` for string representation "

"including all sublists"

msgstr ""

#: ../../whatsnew/3.2.rst:734

msgid ""

":meth:`xml.etree.ElementTree.Element.extend` for appending a sequence of "

"zero or more elements"

msgstr ""

#: ../../whatsnew/3.2.rst:736

msgid ""

":meth:`xml.etree.ElementTree.Element.iterfind` searches an element and "

"subelements"

msgstr ""

#: ../../whatsnew/3.2.rst:738

msgid ""

":meth:`xml.etree.ElementTree.Element.itertext` creates a text iterator over "

"an element and its subelements"

msgstr ""

#: ../../whatsnew/3.2.rst:740

msgid ""

":meth:`xml.etree.ElementTree.TreeBuilder.end` closes the current element"

msgstr ""

#: ../../whatsnew/3.2.rst:741

msgid ""

":meth:`xml.etree.ElementTree.TreeBuilder.doctype` handles a doctype "

"declaration"

msgstr ""

#: ../../whatsnew/3.2.rst:744

msgid "Two methods have been deprecated:"

msgstr ""

#: ../../whatsnew/3.2.rst:746

msgid ":meth:`xml.etree.ElementTree.getchildren` use ``list(elem)`` instead."

msgstr ""

#: ../../whatsnew/3.2.rst:747

msgid ":meth:`xml.etree.ElementTree.getiterator` use ``Element.iter`` instead."

msgstr ""

#: ../../whatsnew/3.2.rst:749

msgid ""

"For details of the update, see `Introducing ElementTree <https://web.archive."

"org/web/20200703234532/http://effbot.org/zone/elementtree-13-intro.htm>`_ on "

"Fredrik Lundh's website."

msgstr ""

#: ../../whatsnew/3.2.rst:753

msgid "(Contributed by Florent Xicluna and Fredrik Lundh, :issue:`6472`.)"

msgstr "（由 Florent Xicluna 和 Fredrik Lundh 貢獻，:issue:`6472`。）"

#: ../../whatsnew/3.2.rst:756

msgid "functools"

msgstr "functools"

#: ../../whatsnew/3.2.rst:758

msgid ""

"The :mod:`functools` module includes a new decorator for caching function "

"calls. :func:`functools.lru_cache` can save repeated queries to an external "

"resource whenever the results are expected to be the same."

msgstr ""

#: ../../whatsnew/3.2.rst:762

msgid ""

"For example, adding a caching decorator to a database query function can "

"save database accesses for popular searches:"

msgstr ""

#: ../../whatsnew/3.2.rst:775

msgid ""

"To help with choosing an effective cache size, the wrapped function is "

"instrumented for tracking cache statistics:"

msgstr ""

#: ../../whatsnew/3.2.rst:781

msgid ""

"If the phonelist table gets updated, the outdated contents of the cache can "

"be cleared with:"

msgstr ""

#: ../../whatsnew/3.2.rst:786

msgid ""

"(Contributed by Raymond Hettinger and incorporating design ideas from Jim "

"Baker, Miki Tebeka, and Nick Coghlan; see `recipe 498245 <https://code."

"activestate.com/recipes/498245/>`_\\, `recipe 577479 <https://code."

"activestate.com/recipes/577479/>`_\\, :issue:`10586`, and :issue:`10593`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:792

msgid ""

"The :func:`functools.wraps` decorator now adds a :attr:`__wrapped__` "

"attribute pointing to the original callable function. This allows wrapped "

"functions to be introspected. It also copies :attr:`__annotations__` if "

"defined. And now it also gracefully skips over missing attributes such as :"

"attr:`__doc__` which might not be defined for the wrapped callable."

msgstr ""

#: ../../whatsnew/3.2.rst:798

msgid ""

"In the above example, the cache can be removed by recovering the original "

"function:"

msgstr ""

#: ../../whatsnew/3.2.rst:803

msgid ""

"(By Nick Coghlan and Terrence Cole; :issue:`9567`, :issue:`3445`, and :issue:"

"`8814`.)"

msgstr ""

#: ../../whatsnew/3.2.rst:806

msgid ""

"To help write classes with rich comparison methods, a new decorator :func:"

"`functools.total_ordering` will use existing equality and inequality methods "

"to fill in the remaining methods."

msgstr ""

#: ../../whatsnew/3.2.rst:810

msgid ""

"For example, supplying *__eq__* and *__lt__* will enable :func:`~functools."

"total_ordering` to fill-in *__le__*, *__gt__* and *__ge__*::"

msgstr ""

#: ../../whatsnew/3.2.rst:823

msgid ""

"With the *total_ordering* decorator, the remaining comparison methods are "

"filled in automatically."

msgstr ""

#: ../../whatsnew/3.2.rst:826 ../../whatsnew/3.2.rst:838

#: ../../whatsnew/3.2.rst:882 ../../whatsnew/3.2.rst:903

#: ../../whatsnew/3.2.rst:917 ../../whatsnew/3.2.rst:1787

#: ../../whatsnew/3.2.rst:1831

msgid "(Contributed by Raymond Hettinger.)"

msgstr "（由 Raymond Hettinger 貢獻。）"

#: ../../whatsnew/3.2.rst:828

msgid ""

"To aid in porting programs from Python 2, the :func:`functools.cmp_to_key` "

"function converts an old-style comparison function to modern :term:`key "

"function`:"

msgstr ""

#: ../../whatsnew/3.2.rst:835

msgid ""

"For sorting examples and a brief sorting tutorial, see the `Sorting HowTo "

"<https://wiki.python.org/moin/HowTo/Sorting/>`_ tutorial."

msgstr ""

#: ../../whatsnew/3.2.rst:841

msgid "itertools"

msgstr "itertools"

#: ../../whatsnew/3.2.rst:843

msgid ""

"The :mod:`itertools` module has a new :func:`~itertools.accumulate` function "

"modeled on APL's *scan* operator and Numpy's *accumulate* function:"

msgstr ""

#: ../../whatsnew/3.2.rst:854

msgid ""

"For an example using :func:`~itertools.accumulate`, see the :ref:`examples "

"for the random module <random-examples>`."

msgstr ""

#: ../../whatsnew/3.2.rst:857

msgid ""

"(Contributed by Raymond Hettinger and incorporating design suggestions from "

"Mark Dickinson.)"

msgstr "（由 Raymond Hettinger 貢獻，並結合了 Mark Dickinson 的設計建議。）"

#: ../../whatsnew/3.2.rst:861

msgid "collections"

msgstr "collections"

#: ../../whatsnew/3.2.rst:863

msgid ""

"The :class:`collections.Counter` class now has two forms of in-place "

"subtraction, the existing *-=* operator for `saturating subtraction <https://"

"en.wikipedia.org/wiki/Saturation_arithmetic>`_ and the new :meth:"

"`~collections.Counter.subtract` method for regular subtraction. The former "

"is suitable for `multisets <https://en.wikipedia.org/wiki/Multiset>`_ which "

"only have positive counts, and the latter is more suitable for use cases "

"that allow negative counts:"

msgstr ""

#: ../../whatsnew/3.2.rst:884

msgid ""

"The :class:`collections.OrderedDict` class has a new method :meth:"

"`~collections.OrderedDict.move_to_end` which takes an existing key and moves "

"it to either the first or last position in the ordered sequence."

msgstr ""

#: ../../whatsnew/3.2.rst:888

msgid ""

"The default is to move an item to the last position. This is equivalent of "

"renewing an entry with ``od[k] = od.pop(k)``."

msgstr ""

#: ../../whatsnew/3.2.rst:891

msgid ""

"A fast move-to-end operation is useful for resequencing entries. For "

"example, an ordered dictionary can be used to track order of access by aging "

"entries from the oldest to the most recently accessed."

msgstr ""

#: ../../whatsnew/3.2.rst:905

msgid ""

"The :class:`collections.deque` class grew two new methods :meth:"

"`~collections.deque.count` and :meth:`~collections.deque.reverse` that make "

"them more substitutable for :class:`list` objects:"

msgstr ""

#: ../../whatsnew/3.2.rst:920