# SOME DESCRIPTIVE TITLE.

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

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

# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.

#

#, fuzzy

msgid ""

msgstr ""

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

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

"POT-Creation-Date: 2018-10-23 06:56+0900\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: LANGUAGE <LL@li.org>\n"

"MIME-Version: 1.0\n"

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

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

"Generated-By: Babel 2.5.1\n"

#: ../Doc/whatsnew/3.3.rst:3

msgid "What's New In Python 3.3"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:45

msgid ""

"This article explains the new features in Python 3.3, compared to 3.2. "

"Python 3.3 was released on September 29, 2012. For full details, see the"

" `changelog <https://docs.python.org/3.3/whatsnew/changelog.html>`_."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:51

msgid ":pep:`398` - Python 3.3 Release Schedule"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:55

msgid "Summary -- Release highlights"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:60

msgid "New syntax features:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:62

msgid "New ``yield from`` expression for :ref:`generator delegation <pep-380>`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:63

msgid "The ``u'unicode'`` syntax is accepted again for :class:`str` objects."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:65

msgid "New library modules:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:67

msgid ":mod:`faulthandler` (helps debugging low-level crashes)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:68

msgid ":mod:`ipaddress` (high-level objects representing IP addresses and masks)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:69

msgid ":mod:`lzma` (compress data using the XZ / LZMA algorithm)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:70

msgid ""

":mod:`unittest.mock` (replace parts of your system under test with mock "

"objects)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:71

msgid ""

":mod:`venv` (Python :ref:`virtual environments <pep-405>`, as in the "

"popular ``virtualenv`` package)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:74

msgid "New built-in features:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:76

msgid "Reworked :ref:`I/O exception hierarchy <pep-3151>`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:78

msgid "Implementation improvements:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:80

msgid "Rewritten :ref:`import machinery <importlib>` based on :mod:`importlib`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:81

msgid "More compact :ref:`unicode strings <pep-393>`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:82

msgid "More compact :ref:`attribute dictionaries <pep-412>`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:84

msgid "Significantly Improved Library Modules:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:86

msgid "C Accelerator for the :ref:`decimal <new-decimal>` module."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:87

msgid ""

"Better unicode handling in the :ref:`email <new-email>` module "

"(:term:`provisional <provisional package>`)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:90

msgid "Security improvements:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:92

msgid "Hash randomization is switched on by default."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:94

msgid "Please read on for a comprehensive list of user-facing changes."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:100

msgid "PEP 405: Virtual Environments"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:102

msgid ""

"Virtual environments help create separate Python setups while sharing a "

"system-wide base install, for ease of maintenance. Virtual environments "

"have their own set of private site packages (i.e. locally-installed "

"libraries), and are optionally segregated from the system-wide site "

"packages. Their concept and implementation are inspired by the popular "

"``virtualenv`` third-party package, but benefit from tighter integration "

"with the interpreter core."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:110

msgid ""

"This PEP adds the :mod:`venv` module for programmatic access, and the "

"``pyvenv`` script for command-line access and administration. The Python"

" interpreter checks for a ``pyvenv.cfg``, file whose existence signals "

"the base of a virtual environment's directory tree."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:118

msgid ":pep:`405` - Python Virtual Environments"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:119

msgid "PEP written by Carl Meyer; implementation by Carl Meyer and Vinay Sajip"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:123

msgid "PEP 420: Implicit Namespace Packages"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:125

msgid ""

"Native support for package directories that don't require ``__init__.py``"

" marker files and can automatically span multiple path segments (inspired"

" by various third party approaches to namespace packages, as described in"

" :pep:`420`)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:133

msgid ":pep:`420` - Implicit Namespace Packages"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:133

msgid ""

"PEP written by Eric V. Smith; implementation by Eric V. Smith and Barry "

"Warsaw"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:140

msgid "PEP 3118: New memoryview implementation and buffer protocol documentation"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:142

msgid "The implementation of :pep:`3118` has been significantly improved."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:144

msgid ""

"The new memoryview implementation comprehensively fixes all ownership and"

" lifetime issues of dynamically allocated fields in the Py_buffer struct "

"that led to multiple crash reports. Additionally, several functions that "

"crashed or returned incorrect results for non-contiguous or multi-"

"dimensional input have been fixed."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:150

msgid ""

"The memoryview object now has a PEP-3118 compliant getbufferproc() that "

"checks the consumer's request type. Many new features have been added, "

"most of them work in full generality for non-contiguous arrays and arrays"

" with suboffsets."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:155

msgid ""

"The documentation has been updated, clearly spelling out responsibilities"

" for both exporters and consumers. Buffer request flags are grouped into "

"basic and compound flags. The memory layout of non-contiguous and multi-"

"dimensional NumPy-style arrays is explained."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:161 ../Doc/whatsnew/3.3.rst:1122

msgid "Features"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:163

msgid ""

"All native single character format specifiers in struct module syntax "

"(optionally prefixed with '@') are now supported."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:166

msgid ""

"With some restrictions, the cast() method allows changing of format and "

"shape of C-contiguous arrays."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:169

msgid "Multi-dimensional list representations are supported for any array type."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:171

msgid "Multi-dimensional comparisons are supported for any array type."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:173

msgid ""

"One-dimensional memoryviews of hashable (read-only) types with formats B,"

" b or c are now hashable. (Contributed by Antoine Pitrou in "

":issue:`13411`.)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:176

msgid ""

"Arbitrary slicing of any 1-D arrays type is supported. For example, it is"

" now possible to reverse a memoryview in O(1) by using a negative step."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:180 ../Doc/whatsnew/3.3.rst:1132

msgid "API changes"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:182

msgid "The maximum number of dimensions is officially limited to 64."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:184

msgid ""

"The representation of empty shape, strides and suboffsets is now an empty"

" tuple instead of ``None``."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:187

msgid ""

"Accessing a memoryview element with format 'B' (unsigned bytes) now "

"returns an integer (in accordance with the struct module syntax). For "

"returning a bytes object the view must be cast to 'c' first."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:191

msgid ""

"memoryview comparisons now use the logical structure of the operands and "

"compare all array elements by value. All format strings in struct module "

"syntax are supported. Views with unrecognised format strings are still "

"permitted, but will always compare as unequal, regardless of view "

"contents."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:197

msgid "For further changes see `Build and C API Changes`_ and `Porting C code`_."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:199

msgid "(Contributed by Stefan Krah in :issue:`10181`.)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:203

msgid ":pep:`3118` - Revising the Buffer Protocol"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:209

msgid "PEP 393: Flexible String Representation"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:211

msgid ""

"The Unicode string type is changed to support multiple internal "

"representations, depending on the character with the largest Unicode "

"ordinal (1, 2, or 4 bytes) in the represented string. This allows a "

"space-efficient representation in common cases, but gives access to full "

"UCS-4 on all systems. For compatibility with existing APIs, several "

"representations may exist in parallel; over time, this compatibility "

"should be phased out."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:218

msgid "On the Python side, there should be no downside to this change."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:220

msgid ""

"On the C API side, PEP 393 is fully backward compatible. The legacy API "

"should remain available at least five years. Applications using the "

"legacy API will not fully benefit of the memory reduction, or - worse - "

"may use a bit more memory, because Python may have to maintain two "

"versions of each string (in the legacy format and in the new efficient "

"storage)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:227

msgid "Functionality"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:229

msgid "Changes introduced by :pep:`393` are the following:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:231

msgid ""

"Python now always supports the full range of Unicode code points, "

"including non-BMP ones (i.e. from ``U+0000`` to ``U+10FFFF``). The "

"distinction between narrow and wide builds no longer exists and Python "

"now behaves like a wide build, even under Windows."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:236

msgid ""

"With the death of narrow builds, the problems specific to narrow builds "

"have also been fixed, for example:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:239

msgid ""

":func:`len` now always returns 1 for non-BMP characters, so "

"``len('\\U0010FFFF') == 1``;"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:242

msgid ""

"surrogate pairs are not recombined in string literals, so "

"``'\\uDBFF\\uDFFF' != '\\U0010FFFF'``;"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:245

msgid ""

"indexing or slicing non-BMP characters returns the expected value, so "

"``'\\U0010FFFF'[0]`` now returns ``'\\U0010FFFF'`` and not ``'\\uDBFF'``;"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:248

msgid ""

"all other functions in the standard library now correctly handle non-BMP "

"code points."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:251

msgid ""

"The value of :data:`sys.maxunicode` is now always ``1114111`` "

"(``0x10FFFF`` in hexadecimal). The :c:func:`PyUnicode_GetMax` function "

"still returns either ``0xFFFF`` or ``0x10FFFF`` for backward "

"compatibility, and it should not be used with the new Unicode API (see "

":issue:`13054`)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:256

msgid "The :file:`./configure` flag ``--with-wide-unicode`` has been removed."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:259

msgid "Performance and resource usage"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:261

msgid ""

"The storage of Unicode strings now depends on the highest code point in "

"the string:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:263

msgid ""

"pure ASCII and Latin1 strings (``U+0000-U+00FF``) use 1 byte per code "

"point;"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:265

msgid "BMP strings (``U+0000-U+FFFF``) use 2 bytes per code point;"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:267

msgid "non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per code point."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:269

msgid ""

"The net effect is that for most applications, memory usage of string "

"storage should decrease significantly - especially compared to former "

"wide unicode builds - as, in many cases, strings will be pure ASCII even "

"in international contexts (because many strings store non-human language "

"data, such as XML fragments, HTTP headers, JSON-encoded data, etc.). We "

"also hope that it will, for the same reasons, increase CPU cache "

"efficiency on non-trivial applications. The memory usage of Python 3.3 is"

" two to three times smaller than Python 3.2, and a little bit better than"

" Python 2.7, on a Django benchmark (see the PEP for details)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:283

msgid ":pep:`393` - Flexible String Representation"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:283

msgid ""

"PEP written by Martin von Löwis; implementation by Torsten Becker and "

"Martin von Löwis."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:290

msgid "PEP 397: Python Launcher for Windows"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:292

msgid ""

"The Python 3.3 Windows installer now includes a ``py`` launcher "

"application that can be used to launch Python applications in a version "

"independent fashion."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:296

msgid ""

"This launcher is invoked implicitly when double-clicking ``*.py`` files. "

"If only a single Python version is installed on the system, that version "

"will be used to run the file. If multiple versions are installed, the "

"most recent version is used by default, but this can be overridden by "

"including a Unix-style \"shebang line\" in the Python script."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:302

msgid ""

"The launcher can also be used explicitly from the command line as the "

"``py`` application. Running ``py`` follows the same version selection "

"rules as implicitly launching scripts, but a more specific version can be"

" selected by passing appropriate arguments (such as ``-3`` to request "

"Python 3 when Python 2 is also installed, or ``-2.6`` to specifically "

"request an earlier Python version when a more recent version is "

"installed)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:309

msgid ""

"In addition to the launcher, the Windows installer now includes an option"

" to add the newly installed Python to the system PATH. (Contributed by "

"Brian Curtin in :issue:`3561`.)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:317

msgid ":pep:`397` - Python Launcher for Windows"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:316

msgid ""

"PEP written by Mark Hammond and Martin v. Löwis; implementation by Vinay "

"Sajip."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:319

msgid "Launcher documentation: :ref:`launcher`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:321

msgid "Installer PATH modification: :ref:`windows-path-mod`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:327

msgid "PEP 3151: Reworking the OS and IO exception hierarchy"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:329

msgid ""

"The hierarchy of exceptions raised by operating system errors is now both"

" simplified and finer-grained."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:332

msgid ""

"You don't have to worry anymore about choosing the appropriate exception "

"type between :exc:`OSError`, :exc:`IOError`, :exc:`EnvironmentError`, "

":exc:`WindowsError`, :exc:`mmap.error`, :exc:`socket.error` or "

":exc:`select.error`. All these exception types are now only one: "

":exc:`OSError`. The other names are kept as aliases for compatibility "

"reasons."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:339

msgid ""

"Also, it is now easier to catch a specific error condition. Instead of "

"inspecting the ``errno`` attribute (or ``args[0]``) for a particular "

"constant from the :mod:`errno` module, you can catch the adequate "

":exc:`OSError` subclass. The available subclasses are the following:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:344

msgid ":exc:`BlockingIOError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:345

msgid ":exc:`ChildProcessError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:346

msgid ":exc:`ConnectionError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:347

msgid ":exc:`FileExistsError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:348

msgid ":exc:`FileNotFoundError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:349

msgid ":exc:`InterruptedError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:350

msgid ":exc:`IsADirectoryError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:351

msgid ":exc:`NotADirectoryError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:352

msgid ":exc:`PermissionError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:353

msgid ":exc:`ProcessLookupError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:354

msgid ":exc:`TimeoutError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:356

msgid "And the :exc:`ConnectionError` itself has finer-grained subclasses:"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:358

msgid ":exc:`BrokenPipeError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:359

msgid ":exc:`ConnectionAbortedError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:360

msgid ":exc:`ConnectionRefusedError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:361

msgid ":exc:`ConnectionResetError`"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:363

msgid ""

"Thanks to the new exceptions, common usages of the :mod:`errno` can now "

"be avoided. For example, the following code written for Python 3.2::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:379

msgid ""

"can now be written without the :mod:`errno` import and without manual "

"inspection of exception attributes::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:392

msgid ":pep:`3151` - Reworking the OS and IO Exception Hierarchy"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:393

msgid "PEP written and implemented by Antoine Pitrou"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:402

msgid "PEP 380: Syntax for Delegating to a Subgenerator"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:404

msgid ""

"PEP 380 adds the ``yield from`` expression, allowing a :term:`generator` "

"to delegate part of its operations to another generator. This allows a "

"section of code containing :keyword:`yield` to be factored out and placed"

" in another generator. Additionally, the subgenerator is allowed to "

"return with a value, and the value is made available to the delegating "

"generator."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:411

msgid ""

"While designed primarily for use in delegating to a subgenerator, the "

"``yield from`` expression actually allows delegation to arbitrary "

"subiterators."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:414

msgid ""

"For simple iterators, ``yield from iterable`` is essentially just a "

"shortened form of ``for item in iterable: yield item``::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:424

msgid ""

"However, unlike an ordinary loop, ``yield from`` allows subgenerators to "

"receive sent and thrown values directly from the calling scope, and "

"return a final value to the outer generator::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:455

msgid ""

"The main principle driving this change is to allow even generators that "

"are designed to be used with the ``send`` and ``throw`` methods to be "

"split into multiple subgenerators as easily as a single large function "

"can be split into multiple subfunctions."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:464

msgid ":pep:`380` - Syntax for Delegating to a Subgenerator"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:463

msgid ""

"PEP written by Greg Ewing; implementation by Greg Ewing, integrated into "

"3.3 by Renaud Blanch, Ryan Kelly and Nick Coghlan; documentation by "

"Zbigniew Jędrzejewski-Szmek and Nick Coghlan"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:469

msgid "PEP 409: Suppressing exception context"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:471

msgid ""

"PEP 409 introduces new syntax that allows the display of the chained "

"exception context to be disabled. This allows cleaner error messages in "

"applications that convert between exception types::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:490

msgid ""

"Without the ``from None`` suffix to suppress the cause, the original "

"exception would be displayed by default::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:514

msgid ""

"No debugging capability is lost, as the original exception context "

"remains available if needed (for example, if an intervening library has "

"incorrectly suppressed valuable underlying details)::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:528

msgid ":pep:`409` - Suppressing exception context"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:528

msgid "PEP written by Ethan Furman; implemented by Ethan Furman and Nick Coghlan."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:533

msgid "PEP 414: Explicit Unicode literals"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:535

msgid ""

"To ease the transition from Python 2 for Unicode aware Python "

"applications that make heavy use of Unicode literals, Python 3.3 once "

"again supports the \"``u``\" prefix for string literals. This prefix has "

"no semantic significance in Python 3, it is provided solely to reduce the"

" number of purely mechanical changes in migrating to Python 3, making it "

"easier for developers to focus on the more significant semantic changes "

"(such as the stricter default separation of binary and text data)."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:545

msgid ":pep:`414` - Explicit Unicode literals"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:546

msgid "PEP written by Armin Ronacher."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:550

msgid "PEP 3155: Qualified name for classes and functions"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:552

msgid ""

"Functions and class objects have a new ``__qualname__`` attribute "

"representing the \"path\" from the module top-level to their definition."

" For global functions and classes, this is the same as ``__name__``. "

"For other functions and classes, it provides better information about "

"where they were actually defined, and how they might be accessible from "

"the global scope."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:558

msgid "Example with (non-bound) methods::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:568

msgid "Example with nested classes::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:584

msgid "Example with nested functions::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:596

msgid ""

"The string representation of those objects is also changed to include the"

" new, more precise information::"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:606

msgid ":pep:`3155` - Qualified name for classes and functions"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:607

msgid "PEP written and implemented by Antoine Pitrou."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:613

msgid "PEP 412: Key-Sharing Dictionary"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:615

msgid ""

"Dictionaries used for the storage of objects' attributes are now able to "

"share part of their internal storage between each other (namely, the part"

" which stores the keys and their respective hashes). This reduces the "

"memory consumption of programs creating many instances of non-builtin "

"types."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:622

msgid ":pep:`412` - Key-Sharing Dictionary"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:623

msgid "PEP written and implemented by Mark Shannon."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:627

msgid "PEP 362: Function Signature Object"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:629

msgid ""

"A new function :func:`inspect.signature` makes introspection of python "

"callables easy and straightforward. A broad range of callables is "

"supported: python functions, decorated or not, classes, and "

":func:`functools.partial` objects. New classes "

":class:`inspect.Signature`, :class:`inspect.Parameter` and "

":class:`inspect.BoundArguments` hold information about the call "

"signatures, such as, annotations, default values, parameters kinds, and "

"bound arguments, which considerably simplifies writing decorators and any"

" code that validates or amends calling signatures or arguments."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:641

msgid ":pep:`362`: - Function Signature Object"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:641

msgid ""

"PEP written by Brett Cannon, Yury Selivanov, Larry Hastings, Jiwon Seo; "

"implemented by Yury Selivanov."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:646

msgid "PEP 421: Adding sys.implementation"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:648

msgid ""

"A new attribute on the :mod:`sys` module exposes details specific to the "

"implementation of the currently running interpreter. The initial set of "

"attributes on :attr:`sys.implementation` are ``name``, ``version``, "

"``hexversion``, and ``cache_tag``."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:653

msgid ""

"The intention of ``sys.implementation`` is to consolidate into one "

"namespace the implementation-specific data used by the standard library."

" This allows different Python implementations to share a single standard"

" library code base much more easily. In its initial state, "

"``sys.implementation`` holds only a small portion of the implementation-"

"specific data. Over time that ratio will shift in order to make the "

"standard library more portable."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:660

msgid ""

"One example of improved standard library portability is ``cache_tag``. "

"As of Python 3.3, ``sys.implementation.cache_tag`` is used by "

":mod:`importlib` to support :pep:`3147` compliance. Any Python "

"implementation that uses ``importlib`` for its built-in import system may"

" use ``cache_tag`` to control the caching behavior for modules."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:667

msgid "SimpleNamespace"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:669

msgid ""

"The implementation of ``sys.implementation`` also introduces a new type "

"to Python: :class:`types.SimpleNamespace`. In contrast to a mapping-"

"based namespace, like :class:`dict`, ``SimpleNamespace`` is attribute-"

"based, like :class:`object`. However, unlike ``object``, "

"``SimpleNamespace`` instances are writable. This means that you can add,"

" remove, and modify the namespace through normal attribute access."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:678

msgid ":pep:`421` - Adding sys.implementation"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:679

msgid "PEP written and implemented by Eric Snow."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:685

msgid "Using importlib as the Implementation of Import"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:686

msgid ""

":issue:`2377` - Replace __import__ w/ importlib.__import__ :issue:`13959`"

" - Re-implement parts of :mod:`imp` in pure Python :issue:`14605` - Make "

"import machinery explicit :issue:`14646` - Require loaders set __loader__"

" and __package__"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:691

msgid ""

"The :func:`__import__` function is now powered by "

":func:`importlib.__import__`. This work leads to the completion of "

"\"phase 2\" of :pep:`302`. There are multiple benefits to this change. "

"First, it has allowed for more of the machinery powering import to be "

"exposed instead of being implicit and hidden within the C code. It also "

"provides a single implementation for all Python VMs supporting Python 3.3"

" to use, helping to end any VM-specific deviations in import semantics. "

"And finally it eases the maintenance of import, allowing for future "

"growth to occur."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:700

msgid ""

"For the common user, there should be no visible change in semantics. For"

" those whose code currently manipulates import or calls import "

"programmatically, the code changes that might possibly be required are "

"covered in the `Porting Python code`_ section of this document."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:706

msgid "New APIs"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:707

msgid ""

"One of the large benefits of this work is the exposure of what goes into "

"making the import statement work. That means the various importers that "

"were once implicit are now fully exposed as part of the :mod:`importlib` "

"package."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:711

msgid ""

"The abstract base classes defined in :mod:`importlib.abc` have been "

"expanded to properly delineate between :term:`meta path finders <meta "

"path finder>` and :term:`path entry finders <path entry finder>` by "

"introducing :class:`importlib.abc.MetaPathFinder` and "

":class:`importlib.abc.PathEntryFinder`, respectively. The old ABC of "

":class:`importlib.abc.Finder` is now only provided for backwards-"

"compatibility and does not enforce any method requirements."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:719

msgid ""

"In terms of finders, :class:`importlib.machinery.FileFinder` exposes the "

"mechanism used to search for source and bytecode files of a module. "

"Previously this class was an implicit member of :attr:`sys.path_hooks`."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:723

msgid ""

"For loaders, the new abstract base class "

":class:`importlib.abc.FileLoader` helps write a loader that uses the file"

" system as the storage mechanism for a module's code. The loader for "

"source files (:class:`importlib.machinery.SourceFileLoader`), sourceless "

"bytecode files (:class:`importlib.machinery.SourcelessFileLoader`), and "

"extension modules (:class:`importlib.machinery.ExtensionFileLoader`) are "

"now available for direct use."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:731

msgid ""

":exc:`ImportError` now has ``name`` and ``path`` attributes which are set"

" when there is relevant data to provide. The message for failed imports "

"will also provide the full name of the module now instead of just the "

"tail end of the module's name."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:736

msgid ""

"The :func:`importlib.invalidate_caches` function will now call the method"

" with the same name on all finders cached in "

":attr:`sys.path_importer_cache` to help clean up any stored state as "

"necessary."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:741

msgid "Visible Changes"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:743

msgid ""

"For potential required changes to code, see the `Porting Python code`_ "

"section."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:746

msgid ""

"Beyond the expanse of what :mod:`importlib` now exposes, there are other "

"visible changes to import. The biggest is that :attr:`sys.meta_path` and "

":attr:`sys.path_hooks` now store all of the meta path finders and path "

"entry hooks used by import. Previously the finders were implicit and "

"hidden within the C code of import instead of being directly exposed. "

"This means that one can now easily remove or change the order of the "

"various finders to fit one's needs."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:753

msgid ""

"Another change is that all modules have a ``__loader__`` attribute, "

"storing the loader used to create the module. :pep:`302` has been updated"

" to make this attribute mandatory for loaders to implement, so in the "

"future once 3rd-party loaders have been updated people will be able to "

"rely on the existence of the attribute. Until such time, though, import "

"is setting the module post-load."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:759

msgid ""

"Loaders are also now expected to set the ``__package__`` attribute from "

":pep:`366`. Once again, import itself is already setting this on all "

"loaders from :mod:`importlib` and import itself is setting the attribute "

"post-load."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:763

msgid ""

"``None`` is now inserted into :attr:`sys.path_importer_cache` when no "

"finder can be found on :attr:`sys.path_hooks`. Since "

":class:`imp.NullImporter` is not directly exposed on "

":attr:`sys.path_hooks` it could no longer be relied upon to always be "

"available to use as a value representing no finder found."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:768

msgid ""

"All other changes relate to semantic changes which should be taken into "

"consideration when updating code for Python 3.3, and thus should be read "

"about in the `Porting Python code`_ section of this document."

msgstr ""

#: ../Doc/whatsnew/3.3.rst:772

msgid "(Implementation by Brett Cannon)"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:776

msgid "Other Language Changes"

msgstr ""

#: ../Doc/whatsnew/3.3.rst:778