# SOME DESCRIPTIVE TITLE.

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

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

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#

# Translators:

# python-doc bot, 2025

#

#, fuzzy

msgid ""

msgstr ""

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

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

"POT-Creation-Date: 2026-04-09 17:33+0000\n"

"PO-Revision-Date: 2025-09-22 16:51+0000\n"

"Last-Translator: python-doc bot, 2025\n"

"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"

"MIME-Version: 1.0\n"

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

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

"Language: pl\n"

"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "

"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "

"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"

msgid "What's New in Python 2.6"

msgstr ""

msgid "Author"

msgstr "Autor"

msgid "A.M. Kuchling (amk at amk.ca)"

msgstr ""

msgid ""

"This article explains the new features in Python 2.6, released on October 1, "

"2008. The release schedule is described in :pep:`361`."

msgstr ""

msgid ""

"The major theme of Python 2.6 is preparing the migration path to Python 3.0, "

"a major redesign of the language. Whenever possible, Python 2.6 "

"incorporates new features and syntax from 3.0 while remaining compatible "

"with existing code by not removing older features or syntax. When it's not "

"possible to do that, Python 2.6 tries to do what it can, adding "

"compatibility functions in a :mod:`future_builtins` module and a :option:"

"`!-3` switch to warn about usages that will become unsupported in 3.0."

msgstr ""

msgid ""

"Some significant new packages have been added to the standard library, such "

"as the :mod:`multiprocessing` and :mod:`json` modules, but there aren't many "

"new features that aren't related to Python 3.0 in some way."

msgstr ""

msgid ""

"Python 2.6 also sees a number of improvements and bugfixes throughout the "

"source. A search through the change logs finds there were 259 patches "

"applied and 612 bugs fixed between Python 2.5 and 2.6. Both figures are "

"likely to be underestimates."

msgstr ""

msgid ""

"This article doesn't attempt to provide a complete specification of the new "

"features, but instead provides a convenient overview. For full details, you "

"should refer to the documentation for Python 2.6. If you want to understand "

"the rationale for the design and implementation, refer to the PEP for a "

"particular new feature. Whenever possible, \"What's New in Python\" links to "

"the bug/patch item for each change."

msgstr ""

msgid "Python 3.0"

msgstr ""

msgid ""

"The development cycle for Python versions 2.6 and 3.0 was synchronized, with "

"the alpha and beta releases for both versions being made on the same days. "

"The development of 3.0 has influenced many features in 2.6."

msgstr ""

msgid ""

"Python 3.0 is a far-ranging redesign of Python that breaks compatibility "

"with the 2.x series. This means that existing Python code will need some "

"conversion in order to run on Python 3.0. However, not all the changes in "

"3.0 necessarily break compatibility. In cases where new features won't "

"cause existing code to break, they've been backported to 2.6 and are "

"described in this document in the appropriate place. Some of the 3.0-"

"derived features are:"

msgstr ""

msgid ""

"A :meth:`__complex__` method for converting objects to a complex number."

msgstr ""

msgid "Alternate syntax for catching exceptions: ``except TypeError as exc``."

msgstr ""

msgid ""

"The addition of :func:`functools.reduce` as a synonym for the built-in :func:"

"`reduce` function."

msgstr ""

msgid ""

"Python 3.0 adds several new built-in functions and changes the semantics of "

"some existing builtins. Functions that are new in 3.0 such as :func:`bin` "

"have simply been added to Python 2.6, but existing builtins haven't been "

"changed; instead, the :mod:`future_builtins` module has versions with the "

"new 3.0 semantics. Code written to be compatible with 3.0 can do ``from "

"future_builtins import hex, map`` as necessary."

msgstr ""

msgid ""

"A new command-line switch, :option:`!-3`, enables warnings about features "

"that will be removed in Python 3.0. You can run code with this switch to "

"see how much work will be necessary to port code to 3.0. The value of this "

"switch is available to Python code as the boolean variable :data:`sys."

"py3kwarning`, and to C extension code as :c:data:`Py_Py3kWarningFlag`."

msgstr ""

msgid ""

"The 3\\ *xxx* series of PEPs, which contains proposals for Python 3.0. :pep:"

"`3000` describes the development process for Python 3.0. Start with :pep:"

"`3100` that describes the general goals for Python 3.0, and then explore the "

"higher-numbered PEPs that propose specific features."

msgstr ""

msgid "Changes to the Development Process"

msgstr ""

msgid ""

"While 2.6 was being developed, the Python development process underwent two "

"significant changes: we switched from SourceForge's issue tracker to a "

"customized Roundup installation, and the documentation was converted from "

"LaTeX to reStructuredText."

msgstr ""

msgid "New Issue Tracker: Roundup"

msgstr ""

msgid ""

"For a long time, the Python developers had been growing increasingly annoyed "

"by SourceForge's bug tracker. SourceForge's hosted solution doesn't permit "

"much customization; for example, it wasn't possible to customize the life "

"cycle of issues."

msgstr ""

msgid ""

"The infrastructure committee of the Python Software Foundation therefore "

"posted a call for issue trackers, asking volunteers to set up different "

"products and import some of the bugs and patches from SourceForge. Four "

"different trackers were examined: `Jira <https://www.atlassian.com/software/"

"jira/>`__, `Launchpad <https://launchpad.net/>`__, `Roundup <https://roundup."

"sourceforge.io/>`__, and `Trac <https://trac.edgewall.org/>`__. The "

"committee eventually settled on Jira and Roundup as the two candidates. "

"Jira is a commercial product that offers no-cost hosted instances to free-"

"software projects; Roundup is an open-source project that requires "

"volunteers to administer it and a server to host it."

msgstr ""

msgid ""

"After posting a call for volunteers, a new Roundup installation was set up "

"at https://bugs.python.org. One installation of Roundup can host multiple "

"trackers, and this server now also hosts issue trackers for Jython and for "

"the Python web site. It will surely find other uses in the future. Where "

"possible, this edition of \"What's New in Python\" links to the bug/patch "

"item for each change."

msgstr ""

msgid ""

"Hosting of the Python bug tracker is kindly provided by `Upfront Systems "

"<https://upfrontsoftware.co.za>`__ of Stellenbosch, South Africa. Martin "

"von Löwis put a lot of effort into importing existing bugs and patches from "

"SourceForge; his scripts for this import operation are at ``https://svn."

"python.org/view/tracker/importer/`` and may be useful to other projects "

"wishing to move from SourceForge to Roundup."

msgstr ""

msgid "https://bugs.python.org"

msgstr "https://bugs.python.org"

msgid "The Python bug tracker."

msgstr ""

msgid "https://bugs.jython.org:"

msgstr "https://bugs.jython.org:"

msgid "The Jython bug tracker."

msgstr ""

msgid "https://roundup.sourceforge.io/"

msgstr "https://roundup.sourceforge.io/"

msgid "Roundup downloads and documentation."

msgstr ""

msgid "https://svn.python.org/view/tracker/importer/"

msgstr "https://svn.python.org/view/tracker/importer/"

msgid "Martin von Löwis's conversion scripts."

msgstr ""

msgid "New Documentation Format: reStructuredText Using Sphinx"

msgstr ""

msgid ""

"The Python documentation was written using LaTeX since the project started "

"around 1989. In the 1980s and early 1990s, most documentation was printed "

"out for later study, not viewed online. LaTeX was widely used because it "

"provided attractive printed output while remaining straightforward to write "

"once the basic rules of the markup were learned."

msgstr ""

msgid ""

"Today LaTeX is still used for writing publications destined for printing, "

"but the landscape for programming tools has shifted. We no longer print out "

"reams of documentation; instead, we browse through it online and HTML has "

"become the most important format to support. Unfortunately, converting LaTeX "

"to HTML is fairly complicated and Fred L. Drake Jr., the long-time Python "

"documentation editor, spent a lot of time maintaining the conversion "

"process. Occasionally people would suggest converting the documentation "

"into SGML and later XML, but performing a good conversion is a major task "

"and no one ever committed the time required to finish the job."

msgstr ""

msgid ""

"During the 2.6 development cycle, Georg Brandl put a lot of effort into "

"building a new toolchain for processing the documentation. The resulting "

"package is called Sphinx, and is available from https://www.sphinx-doc.org/."

msgstr ""

msgid ""

"Sphinx concentrates on HTML output, producing attractively styled and modern "

"HTML; printed output is still supported through conversion to LaTeX. The "

"input format is reStructuredText, a markup syntax supporting custom "

"extensions and directives that is commonly used in the Python community."

msgstr ""

msgid ""

"Sphinx is a standalone package that can be used for writing, and almost two "

"dozen other projects (`listed on the Sphinx web site <https://www.sphinx-doc."

"org/en/master/examples.html>`__) have adopted Sphinx as their documentation "

"tool."

msgstr ""

msgid "`Documenting Python <https://devguide.python.org/documenting/>`__"

msgstr ""

msgid "Describes how to write for Python's documentation."

msgstr ""

msgid "`Sphinx <https://www.sphinx-doc.org/>`__"

msgstr "`Sphinx <https://www.sphinx-doc.org/>`__"

msgid "Documentation and code for the Sphinx toolchain."

msgstr ""

msgid "`Docutils <https://docutils.sourceforge.io>`__"

msgstr ""

msgid "The underlying reStructuredText parser and toolset."

msgstr ""

msgid "PEP 343: The 'with' statement"

msgstr ""

msgid ""

"The previous version, Python 2.5, added the ':keyword:`with`' statement as "

"an optional feature, to be enabled by a ``from __future__ import "

"with_statement`` directive. In 2.6 the statement no longer needs to be "

"specially enabled; this means that :keyword:`!with` is now always a "

"keyword. The rest of this section is a copy of the corresponding section "

"from the \"What's New in Python 2.5\" document; if you're familiar with the "

"':keyword:`!with`' statement from Python 2.5, you can skip this section."

msgstr ""

msgid ""

"The ':keyword:`with`' statement clarifies code that previously would use "

"``try...finally`` blocks to ensure that clean-up code is executed. In this "

"section, I'll discuss the statement as it will commonly be used. In the "

"next section, I'll examine the implementation details and show how to write "

"objects for use with this statement."

msgstr ""

msgid ""

"The ':keyword:`with`' statement is a control-flow structure whose basic "

"structure is::"

msgstr ""

msgid ""

"The expression is evaluated, and it should result in an object that supports "

"the context management protocol (that is, has :meth:`~object.__enter__` and :"

"meth:`~object.__exit__` methods)."

msgstr ""

msgid ""

"The object's :meth:`~object.__enter__` is called before *with-block* is "

"executed and therefore can run set-up code. It also may return a value that "

"is bound to the name *variable*, if given. (Note carefully that *variable* "

"is *not* assigned the result of *expression*.)"

msgstr ""

msgid ""

"After execution of the *with-block* is finished, the object's :meth:`~object."

"__exit__` method is called, even if the block raised an exception, and can "

"therefore run clean-up code."

msgstr ""

msgid ""

"Some standard Python objects now support the context management protocol and "

"can be used with the ':keyword:`with`' statement. File objects are one "

"example::"

msgstr ""

msgid ""

"After this statement has executed, the file object in *f* will have been "

"automatically closed, even if the :keyword:`for` loop raised an exception "

"part-way through the block."

msgstr ""

msgid ""

"In this case, *f* is the same object created by :func:`open`, because :meth:"

"`~object.__enter__` returns *self*."

msgstr ""

msgid ""

"The :mod:`threading` module's locks and condition variables also support "

"the ':keyword:`with`' statement::"

msgstr ""

msgid ""

"The lock is acquired before the block is executed and always released once "

"the block is complete."

msgstr ""

msgid ""

"The :func:`localcontext` function in the :mod:`decimal` module makes it easy "

"to save and restore the current decimal context, which encapsulates the "

"desired precision and rounding characteristics for computations::"

msgstr ""

msgid "Writing Context Managers"

msgstr ""

msgid ""

"Under the hood, the ':keyword:`with`' statement is fairly complicated. Most "

"people will only use ':keyword:`!with`' in company with existing objects and "

"don't need to know these details, so you can skip the rest of this section "

"if you like. Authors of new objects will need to understand the details of "

"the underlying implementation and should keep reading."

msgstr ""

msgid "A high-level explanation of the context management protocol is:"

msgstr ""

msgid ""

"The expression is evaluated and should result in an object called a "

"\"context manager\". The context manager must have :meth:`~object."

"__enter__` and :meth:`~object.__exit__` methods."

msgstr ""

msgid ""

"The context manager's :meth:`~object.__enter__` method is called. The value "

"returned is assigned to *VAR*. If no ``as VAR`` clause is present, the "

"value is simply discarded."

msgstr ""

msgid "The code in *BLOCK* is executed."

msgstr ""

msgid ""

"If *BLOCK* raises an exception, the context manager's :meth:`~object."

"__exit__` method is called with three arguments, the exception details "

"(``type, value, traceback``, the same values returned by :func:`sys."

"exc_info`, which can also be ``None`` if no exception occurred). The "

"method's return value controls whether an exception is re-raised: any false "

"value re-raises the exception, and ``True`` will result in suppressing it. "

"You'll only rarely want to suppress the exception, because if you do the "

"author of the code containing the ':keyword:`with`' statement will never "

"realize anything went wrong."

msgstr ""

msgid ""

"If *BLOCK* didn't raise an exception, the :meth:`~object.__exit__` method "

"is still called, but *type*, *value*, and *traceback* are all ``None``."

msgstr ""

msgid ""

"Let's think through an example. I won't present detailed code but will only "

"sketch the methods necessary for a database that supports transactions."

msgstr ""

msgid ""

"(For people unfamiliar with database terminology: a set of changes to the "

"database are grouped into a transaction. Transactions can be either "

"committed, meaning that all the changes are written into the database, or "

"rolled back, meaning that the changes are all discarded and the database is "

"unchanged. See any database textbook for more information.)"

msgstr ""

msgid ""

"Let's assume there's an object representing a database connection. Our goal "

"will be to let the user write code like this::"

msgstr ""

msgid ""

"The transaction should be committed if the code in the block runs flawlessly "

"or rolled back if there's an exception. Here's the basic interface for :"

"class:`DatabaseConnection` that I'll assume::"

msgstr ""

msgid ""

"The :meth:`~object.__enter__` method is pretty easy, having only to start a "

"new transaction. For this application the resulting cursor object would be "

"a useful result, so the method will return it. The user can then add ``as "

"cursor`` to their ':keyword:`with`' statement to bind the cursor to a "

"variable name. ::"

msgstr ""

msgid ""

"The :meth:`~object.__exit__` method is the most complicated because it's "

"where most of the work has to be done. The method has to check if an "

"exception occurred. If there was no exception, the transaction is "

"committed. The transaction is rolled back if there was an exception."

msgstr ""

msgid ""

"In the code below, execution will just fall off the end of the function, "

"returning the default value of ``None``. ``None`` is false, so the "

"exception will be re-raised automatically. If you wished, you could be more "

"explicit and add a :keyword:`return` statement at the marked location. ::"

msgstr ""

msgid "The contextlib module"

msgstr ""

msgid ""

"The :mod:`contextlib` module provides some functions and a decorator that "

"are useful when writing objects for use with the ':keyword:`with`' statement."

msgstr ""

msgid ""

"The decorator is called :func:`contextmanager`, and lets you write a single "

"generator function instead of defining a new class. The generator should "

"yield exactly one value. The code up to the :keyword:`yield` will be "

"executed as the :meth:`~object.__enter__` method, and the value yielded will "

"be the method's return value that will get bound to the variable in the ':"

"keyword:`with`' statement's :keyword:`!as` clause, if any. The code after "

"the :keyword:`!yield` will be executed in the :meth:`~object.__exit__` "

"method. Any exception raised in the block will be raised by the :keyword:`!"

"yield` statement."

msgstr ""

msgid ""

"Using this decorator, our database example from the previous section could "

"be written as::"

msgstr ""

msgid ""

"The :mod:`contextlib` module also has a ``nested(mgr1, mgr2, ...)`` function "

"that combines a number of context managers so you don't need to write nested "

"':keyword:`with`' statements. In this example, the single ':keyword:`!"

"with`' statement both starts a database transaction and acquires a thread "

"lock::"

msgstr ""

msgid ""

"Finally, the :func:`closing` function returns its argument so that it can be "

"bound to a variable, and calls the argument's ``.close()`` method at the end "

"of the block. ::"

msgstr ""

msgid ":pep:`343` - The \"with\" statement"

msgstr ""

msgid ""

"PEP written by Guido van Rossum and Nick Coghlan; implemented by Mike Bland, "

"Guido van Rossum, and Neal Norwitz. The PEP shows the code generated for a "

"':keyword:`with`' statement, which can be helpful in learning how the "

"statement works."

msgstr ""

msgid "The documentation for the :mod:`contextlib` module."

msgstr ""

msgid "PEP 366: Explicit Relative Imports From a Main Module"

msgstr ""

msgid ""

"Python's :option:`-m` switch allows running a module as a script. When you "

"ran a module that was located inside a package, relative imports didn't work "

"correctly."

msgstr ""

msgid ""

"The fix for Python 2.6 adds a :attr:`__package__` attribute to modules. "

"When this attribute is present, relative imports will be relative to the "

"value of this attribute instead of the :attr:`__name__` attribute."

msgstr ""

msgid ""

"PEP 302-style importers can then set :attr:`__package__` as necessary. The :"

"mod:`runpy` module that implements the :option:`-m` switch now does this, so "

"relative imports will now work correctly in scripts running from inside a "

"package."

msgstr ""

msgid "PEP 370: Per-user ``site-packages`` Directory"

msgstr ""

msgid ""

"When you run Python, the module search path ``sys.path`` usually includes a "

"directory whose path ends in ``\"site-packages\"``. This directory is "

"intended to hold locally installed packages available to all users using a "

"machine or a particular site installation."

msgstr ""

msgid ""

"Python 2.6 introduces a convention for user-specific site directories. The "

"directory varies depending on the platform:"

msgstr ""

msgid "Unix and Mac OS X: :file:`~/.local/`"

msgstr ""

msgid "Windows: :file:`%APPDATA%/Python`"

msgstr "Windows: :file:`%APPDATA%/Python`"

msgid ""

"Within this directory, there will be version-specific subdirectories, such "

"as :file:`lib/python2.6/site-packages` on Unix/Mac OS and :file:`Python26/"

"site-packages` on Windows."

msgstr ""

msgid ""

"If you don't like the default directory, it can be overridden by an "

"environment variable. :envvar:`PYTHONUSERBASE` sets the root directory used "

"for all Python versions supporting this feature. On Windows, the directory "

"for application-specific data can be changed by setting the :envvar:"

"`APPDATA` environment variable. You can also modify the :file:`site.py` "

"file for your Python installation."

msgstr ""

msgid ""

"The feature can be disabled entirely by running Python with the :option:`-s` "

"option or setting the :envvar:`PYTHONNOUSERSITE` environment variable."

msgstr ""

msgid ":pep:`370` - Per-user ``site-packages`` Directory"

msgstr ""

msgid "PEP written and implemented by Christian Heimes."

msgstr ""

msgid "PEP 371: The ``multiprocessing`` Package"

msgstr ""

msgid ""

"The new :mod:`multiprocessing` package lets Python programs create new "

"processes that will perform a computation and return a result to the "

"parent. The parent and child processes can communicate using queues and "

"pipes, synchronize their operations using locks and semaphores, and can "

"share simple arrays of data."

msgstr ""

msgid ""

"The :mod:`multiprocessing` module started out as an exact emulation of the :"

"mod:`threading` module using processes instead of threads. That goal was "

"discarded along the path to Python 2.6, but the general approach of the "

"module is still similar. The fundamental class is the :class:`Process`, "

"which is passed a callable object and a collection of arguments. The :meth:"

"`start` method sets the callable running in a subprocess, after which you "

"can call the :meth:`is_alive` method to check whether the subprocess is "

"still running and the :meth:`join` method to wait for the process to exit."

msgstr ""

msgid ""

"Here's a simple example where the subprocess will calculate a factorial. "

"The function doing the calculation is written strangely so that it takes "

"significantly longer when the input argument is a multiple of 4."

msgstr ""

msgid ""

"A :class:`~queue.Queue` is used to communicate the result of the factorial. "

"The :class:`~queue.Queue` object is stored in a global variable. The child "

"process will use the value of the variable when the child was created; "

"because it's a :class:`~queue.Queue`, parent and child can use the object to "

"communicate. (If the parent were to change the value of the global "

"variable, the child's value would be unaffected, and vice versa.)"

msgstr ""

msgid ""

"Two other classes, :class:`Pool` and :class:`Manager`, provide higher-level "

"interfaces. :class:`Pool` will create a fixed number of worker processes, "

"and requests can then be distributed to the workers by calling :meth:`apply` "

"or :meth:`apply_async` to add a single request, and :meth:`map` or :meth:"

"`map_async` to add a number of requests. The following code uses a :class:"

"`Pool` to spread requests across 5 worker processes and retrieve a list of "

"results::"

msgstr ""

msgid "This produces the following output::"

msgstr ""

msgid ""

"The other high-level interface, the :class:`Manager` class, creates a "

"separate server process that can hold master copies of Python data "

"structures. Other processes can then access and modify these data "

"structures using proxy objects. The following example creates a shared "

"dictionary by calling the :meth:`dict` method; the worker processes then "

"insert values into the dictionary. (Locking is not done for you "

"automatically, which doesn't matter in this example. :class:`Manager`'s "

"methods also include :meth:`Lock`, :meth:`RLock`, and :meth:`Semaphore` to "

"create shared locks.)"

msgstr ""

msgid "This will produce the output::"

msgstr ""

msgid "The documentation for the :mod:`multiprocessing` module."

msgstr ""

msgid ":pep:`371` - Addition of the multiprocessing package"

msgstr ""

msgid ""

"PEP written by Jesse Noller and Richard Oudkerk; implemented by Richard "

"Oudkerk and Jesse Noller."

msgstr ""

msgid "PEP 3101: Advanced String Formatting"

msgstr ""

msgid ""

"In Python 3.0, the ``%`` operator is supplemented by a more powerful string "

"formatting method, :meth:`format`. Support for the :meth:`str.format` "

"method has been backported to Python 2.6."

msgstr ""

msgid ""

"In 2.6, both 8-bit and Unicode strings have a ``.format()`` method that "

"treats the string as a template and takes the arguments to be formatted. The "

"formatting template uses curly brackets (``{``, ``}``) as special "

"characters::"

msgstr ""

msgid "Curly brackets can be escaped by doubling them::"

msgstr ""

msgid ""

"Field names can be integers indicating positional arguments, such as ``{0}"

"``, ``{1}``, etc. or names of keyword arguments. You can also supply "

"compound field names that read attributes or access dictionary keys::"

msgstr ""

msgid ""

"Note that when using dictionary-style notation such as ``[.mp4]``, you don't "

"need to put any quotation marks around the string; it will look up the value "

"using ``.mp4`` as the key. Strings beginning with a number will be "

"converted to an integer. You can't write more complicated expressions "

"inside a format string."

msgstr ""

msgid ""

"So far we've shown how to specify which field to substitute into the "

"resulting string. The precise formatting used is also controllable by "

"adding a colon followed by a format specifier. For example::"

msgstr ""

msgid "Format specifiers can reference other fields through nesting::"

msgstr ""

msgid "The alignment of a field within the desired width can be specified:"

msgstr ""

msgid "Character"

msgstr "Znak"

msgid "Effect"

msgstr ""

msgid "< (default)"

msgstr ""

msgid "Left-align"

msgstr ""

msgid ">"

msgstr ""

msgid "Right-align"

msgstr ""

msgid "^"

msgstr ""

msgid "Center"

msgstr ""

msgid "="

msgstr ""

msgid "(For numeric types only) Pad after the sign."

msgstr ""

msgid ""

"Format specifiers can also include a presentation type, which controls how "

"the value is formatted. For example, floating-point numbers can be "

"formatted as a general number or in exponential notation::"

msgstr ""

msgid ""

"A variety of presentation types are available. Consult the 2.6 "

"documentation for a :ref:`complete list <formatstrings>`; here's a sample:"

msgstr ""

msgid "``b``"

msgstr "``b``"

msgid "Binary. Outputs the number in base 2."

msgstr ""

msgid "``c``"

msgstr "``c``"

msgid ""

"Character. Converts the integer to the corresponding Unicode character "

"before printing."

msgstr ""

msgid "``d``"

msgstr "``d``"

msgid "Decimal Integer. Outputs the number in base 10."

msgstr ""

msgid "``o``"

msgstr "``o``"

msgid "Octal format. Outputs the number in base 8."

msgstr ""

msgid "``x``"

msgstr "``x``"

msgid ""

"Hex format. Outputs the number in base 16, using lower-case letters for the "

"digits above 9."

msgstr ""

msgid "``e``"

msgstr "``e``"

msgid ""

"Exponent notation. Prints the number in scientific notation using the letter "

"'e' to indicate the exponent."

msgstr ""

msgid "``g``"

msgstr "``g``"

msgid ""

"General format. This prints the number as a fixed-point number, unless the "

"number is too large, in which case it switches to 'e' exponent notation."

msgstr ""

msgid "``n``"

msgstr "``n``"

msgid ""

"Number. This is the same as 'g' (for floats) or 'd' (for integers), except "

"that it uses the current locale setting to insert the appropriate number "

"separator characters."

msgstr ""

msgid "``%``"

msgstr "``%``"

msgid ""

"Percentage. Multiplies the number by 100 and displays in fixed ('f') format, "

"followed by a percent sign."

msgstr ""

msgid ""

"Classes and types can define a :meth:`__format__` method to control how "

"they're formatted. It receives a single argument, the format specifier::"

msgstr ""

msgid ""

"There's also a :func:`format` builtin that will format a single value. It "

"calls the type's :meth:`__format__` method with the provided specifier::"

msgstr ""

msgid ":ref:`formatstrings`"

msgstr ":ref:`formatstrings`"

msgid "The reference documentation for format fields."

msgstr ""

msgid ":pep:`3101` - Advanced String Formatting"

msgstr ""

msgid "PEP written by Talin. Implemented by Eric Smith."

msgstr ""

msgid "PEP 3105: ``print`` As a Function"

msgstr ""

msgid ""

"The ``print`` statement becomes the :func:`print` function in Python 3.0. "

"Making :func:`print` a function makes it possible to replace the function by "

"doing ``def print(...)`` or importing a new function from somewhere else."

msgstr ""

msgid ""

"Python 2.6 has a ``__future__`` import that removes ``print`` as language "

"syntax, letting you use the functional form instead. For example::"

msgstr ""

msgid "The signature of the new function is::"

msgstr ""

msgid "The parameters are:"

msgstr ""

msgid "*args*: positional arguments whose values will be printed out."

msgstr ""

msgid "*sep*: the separator, which will be printed between arguments."

msgstr ""

msgid ""

"*end*: the ending text, which will be printed after all of the arguments "

"have been output."

msgstr ""

msgid "*file*: the file object to which the output will be sent."

msgstr ""

msgid ":pep:`3105` - Make print a function"

msgstr ""

msgid "PEP written by Georg Brandl."

msgstr ""

msgid "PEP 3110: Exception-Handling Changes"

msgstr ""

msgid ""

"One error that Python programmers occasionally make is writing the following "

"code::"

msgstr ""

msgid ""

"The author is probably trying to catch both :exc:`TypeError` and :exc:"

"`ValueError` exceptions, but this code actually does something different: it "

"will catch :exc:`TypeError` and bind the resulting exception object to the "

"local name ``\"ValueError\"``. The :exc:`ValueError` exception will not be "

"caught at all. The correct code specifies a tuple of exceptions::"

msgstr ""

msgid ""

"This error happens because the use of the comma here is ambiguous: does it "

"indicate two different nodes in the parse tree, or a single node that's a "

"tuple?"

msgstr ""

msgid ""

"Python 3.0 makes this unambiguous by replacing the comma with the word "

"\"as\". To catch an exception and store the exception object in the "

"variable ``exc``, you must write::"

msgstr ""

msgid ""

"Python 3.0 will only support the use of \"as\", and therefore interprets the "

"first example as catching two different exceptions. Python 2.6 supports "

"both the comma and \"as\", so existing code will continue to work. We "

"therefore suggest using \"as\" when writing new Python code that will only "

"be executed with 2.6."

msgstr ""

msgid ":pep:`3110` - Catching Exceptions in Python 3000"

msgstr ""

msgid "PEP written and implemented by Collin Winter."

msgstr ""

msgid "PEP 3112: Byte Literals"

msgstr ""

msgid ""

"Python 3.0 adopts Unicode as the language's fundamental string type and "

"denotes 8-bit literals differently, either as ``b'string'`` or using a :"

"class:`bytes` constructor. For future compatibility, Python 2.6 adds :class:"

"`bytes` as a synonym for the :class:`str` type, and it also supports the "

"``b''`` notation."

msgstr ""

msgid ""

"The 2.6 :class:`str` differs from 3.0's :class:`bytes` type in various ways; "

"most notably, the constructor is completely different. In 3.0, ``bytes([65, "

"66, 67])`` is 3 elements long, containing the bytes representing ``ABC``; in "

"2.6, ``bytes([65, 66, 67])`` returns the 12-byte string representing the :"

"func:`str` of the list."

msgstr ""

msgid ""

"The primary use of :class:`bytes` in 2.6 will be to write tests of object "

"type such as ``isinstance(x, bytes)``. This will help the 2to3 converter, "

"which can't tell whether 2.x code intends strings to contain either "

"characters or 8-bit bytes; you can now use either :class:`bytes` or :class:"

"`str` to represent your intention exactly, and the resulting code will also "

"be correct in Python 3.0."

msgstr ""

msgid ""

"There's also a ``__future__`` import that causes all string literals to "

"become Unicode strings. This means that ``\\u`` escape sequences can be "

"used to include Unicode characters::"

msgstr ""

msgid ""

"At the C level, Python 3.0 will rename the existing 8-bit string type, "

"called :c:type:`!PyStringObject` in Python 2.x, to :c:type:`PyBytesObject`. "

"Python 2.6 uses ``#define`` to support using the names :c:func:"

"`PyBytesObject`, :c:func:`PyBytes_Check`, :c:func:"

"`PyBytes_FromStringAndSize`, and all the other functions and macros used "

"with strings."

msgstr ""

msgid ""

"Instances of the :class:`bytes` type are immutable just as strings are. A "

"new :class:`bytearray` type stores a mutable sequence of bytes::"

msgstr ""

msgid ""

"Byte arrays support most of the methods of string types, such as :meth:"

"`startswith`/:meth:`endswith`, :meth:`find`/:meth:`rfind`, and some of the "

"methods of lists, such as :meth:`append`, :meth:`pop`, and :meth:`reverse`."

msgstr ""

msgid ""

"There's also a corresponding C API, with :c:func:`PyByteArray_FromObject`, :"

"c:func:`PyByteArray_FromStringAndSize`, and various other functions."

msgstr ""

msgid ":pep:`3112` - Bytes literals in Python 3000"

msgstr ""

msgid "PEP written by Jason Orendorff; backported to 2.6 by Christian Heimes."

msgstr ""

msgid "PEP 3116: New I/O Library"

msgstr ""

msgid ""

"Python's built-in file objects support a number of methods, but file-like "

"objects don't necessarily support all of them. Objects that imitate files "

"usually support :meth:`read` and :meth:`write`, but they may not support :"

"meth:`readline`, for example. Python 3.0 introduces a layered I/O library "

"in the :mod:`io` module that separates buffering and text-handling features "

"from the fundamental read and write operations."

msgstr ""

msgid ""

"There are three levels of abstract base classes provided by the :mod:`io` "

"module:"

msgstr ""

msgid ""

":class:`RawIOBase` defines raw I/O operations: :meth:`read`, :meth:"

"`readinto`, :meth:`write`, :meth:`seek`, :meth:`tell`, :meth:`truncate`, "

"and :meth:`close`. Most of the methods of this class will often map to a "

"single system call. There are also :meth:`readable`, :meth:`writable`, and :"

"meth:`seekable` methods for determining what operations a given object will "

"allow."

msgstr ""

msgid ""

"Python 3.0 has concrete implementations of this class for files and sockets, "

"but Python 2.6 hasn't restructured its file and socket objects in this way."

msgstr ""

msgid ""

":class:`BufferedIOBase` is an abstract base class that buffers data in "

"memory to reduce the number of system calls used, making I/O processing more "

"efficient. It supports all of the methods of :class:`RawIOBase`, and adds a :"

"attr:`raw` attribute holding the underlying raw object."

msgstr ""

msgid ""

"There are five concrete classes implementing this ABC. :class:"

"`BufferedWriter` and :class:`BufferedReader` are for objects that support "

"write-only or read-only usage that have a :meth:`seek` method for random "

"access. :class:`BufferedRandom` objects support read and write access upon "

"the same underlying stream, and :class:`BufferedRWPair` is for objects such "

"as TTYs that have both read and write operations acting upon unconnected "

"streams of data. The :class:`BytesIO` class supports reading, writing, and "

"seeking over an in-memory buffer."

msgstr ""