iframe-proxy | Sunbelt Computer Software

225 lines (176 loc) · 5.63 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 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
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-09-01 17:31+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: Russian (https://app.transifex.com/python-doc/teams/5390/"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
"n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || "
"(n%100>=11 && n%100<=14)? 2 : 3);\n"
msgid ":mod:`!__future__` --- Future statement definitions"
msgid "**Source code:** :source:`Lib/__future__.py`"
"Imports of the form ``from __future__ import feature`` are called :ref:"
"`future statements <future>`. These are special-cased by the Python compiler "
"to allow the use of new Python features in modules containing the future "
"statement before the release in which the feature becomes standard."
"While these future statements are given additional special meaning by the "
"Python compiler, they are still executed like any other import statement and "
"the :mod:`!__future__` exists and is handled by the import system the same "
"way any other Python module would be. This design serves three purposes:"
"To avoid confusing existing tools that analyze import statements and expect "
"to find the modules they're importing."
"To document when incompatible changes were introduced, and when they will be "
"--- or were --- made mandatory.  This is a form of executable documentation, "
"and can be inspected programmatically via importing :mod:`!__future__` and "
"examining its contents."
"To ensure that :ref:`future statements <future>` run under releases prior to "
"Python 2.1 at least yield runtime exceptions (the import of :mod:`!"
"__future__` will fail, because there was no module of that name prior to "
msgid "Module Contents"
"No feature description will ever be deleted from :mod:`!__future__`. Since "
"its introduction in Python 2.1 the following features have found their way "
"into the language using this mechanism:"
msgid "feature"
msgid "optional in"
msgid "mandatory in"
msgid "effect"
msgid "2.1.0b1"
msgid "2.2"
msgid ":pep:`227`: *Statically Nested Scopes*"
msgid "2.2.0a1"
msgid "2.3"
msgid ":pep:`255`: *Simple Generators*"
msgid "2.2.0a2"
msgid "3.0"
msgid ":pep:`238`: *Changing the Division Operator*"
msgid "2.5.0a1"
msgid ":pep:`328`: *Imports: Multi-Line and Absolute/Relative*"
msgid "2.6"
msgid ":pep:`343`: *The “with” Statement*"
msgid "2.6.0a2"
msgid ":pep:`3105`: *Make print a function*"
msgid ":pep:`3112`: *Bytes literals in Python 3000*"
msgid "3.5.0b1"
msgid "3.7"
msgid ":pep:`479`: *StopIteration handling inside generators*"
msgid "3.7.0b1"
msgid "Never [1]_"
":pep:`563`: *Postponed evaluation of annotations*, :pep:`649`: *Deferred "
"evaluation of annotations using descriptors*"
msgid "Each statement in :file:`__future__.py` is of the form::"
"FeatureName = _Feature(OptionalRelease, MandatoryRelease,\n"
"                       CompilerFlag)"
"where, normally, *OptionalRelease* is less than *MandatoryRelease*, and both "
"are 5-tuples of the same form as :data:`sys.version_info`::"
"(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int\n"
" PY_MINOR_VERSION, # the 1; an int\n"
" PY_MICRO_VERSION, # the 0; an int\n"
" PY_RELEASE_LEVEL, # \"alpha\", \"beta\", \"candidate\" or \"final\"; "
" PY_RELEASE_SERIAL # the 3; an int\n"
"*OptionalRelease* records the first release in which the feature was "
"accepted."
"In the case of a *MandatoryRelease* that has not yet occurred, "
"*MandatoryRelease* predicts the release in which the feature will become "
"part of the language."
"Else *MandatoryRelease* records when the feature became part of the "
"language; in releases at or after that, modules no longer need a future "
"statement to use the feature in question, but may continue to use such "
"*MandatoryRelease* may also be ``None``, meaning that a planned feature got "
"dropped or that it is not yet decided."
"*CompilerFlag* is the (bitfield) flag that should be passed in the fourth "
"argument to the built-in function :func:`compile` to enable the feature in "
"dynamically compiled code.  This flag is stored in the :attr:`_Feature."
"compiler_flag` attribute on :class:`_Feature` instances."
"``from __future__ import annotations`` was previously scheduled to become "
"mandatory in Python 3.10, but the change was delayed and ultimately "
"canceled. This feature will eventually be deprecated and removed. See :pep:"
"`649` and :pep:`749`."
msgid ":ref:`future`"
msgid "How the compiler treats future imports."
msgid ":pep:`236` - Back to the __future__"
msgid "The original proposal for the __future__ mechanism."
Sunbelt Computer Software

PL/B Language Development and Support

Navigation Menu

Uh oh!

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

FilesExpand file tree

__future__.po

Latest commit

History

__future__.po

File metadata and controls

future.po

future.po
