diff --git a/locales/ar/LC_MESSAGES/messages.po b/locales/ar/LC_MESSAGES/messages.po index e61f0e4d1..d08026824 100644 --- a/locales/ar/LC_MESSAGES/messages.po +++ b/locales/ar/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-01-19 01:44+0000\n" "Last-Translator: Mohamed Brahimi \n" "Language-Team: Arabic `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8561,7 +8561,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8586,79 +8586,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8666,7 +8632,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8675,7 +8641,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13577,7 +13543,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23028,7 +22994,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23500,7 +23466,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23510,28 +23482,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23542,18 +23514,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23561,22 +23533,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23585,11 +23557,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23599,11 +23571,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23613,11 +23585,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23625,11 +23597,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23640,11 +23612,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23652,11 +23624,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23664,11 +23636,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23678,11 +23650,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23690,11 +23662,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23702,11 +23674,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23714,11 +23686,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23727,11 +23699,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23740,11 +23712,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23754,7 +23726,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23762,69 +23734,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23832,48 +23804,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23884,7 +23856,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23894,17 +23866,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23913,14 +23885,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23931,7 +23903,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23939,30 +23911,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23970,30 +23942,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24001,60 +23973,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24063,79 +24035,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24144,7 +24116,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24152,7 +24124,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24162,21 +24134,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24184,7 +24156,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24193,7 +24165,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24203,14 +24175,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24219,28 +24191,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24249,27 +24221,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24279,7 +24251,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24289,13 +24261,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24515,7 +24487,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24523,7 +24495,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24534,15 +24506,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24550,7 +24522,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24558,7 +24530,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24570,43 +24542,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24615,23 +24587,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/ars/LC_MESSAGES/messages.po b/locales/ars/LC_MESSAGES/messages.po index beab8e098..d8a8c83b4 100644 --- a/locales/ars/LC_MESSAGES/messages.po +++ b/locales/ars/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2713,7 +2713,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "" @@ -3940,7 +3940,7 @@ msgstr "" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "" @@ -8417,12 +8417,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -8436,7 +8436,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8555,7 +8555,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8580,79 +8580,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8660,7 +8626,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8669,7 +8635,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13571,7 +13537,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23022,7 +22988,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23494,7 +23460,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23504,28 +23476,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23536,18 +23508,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23555,22 +23527,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23579,11 +23551,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23593,11 +23565,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23607,11 +23579,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23619,11 +23591,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23634,11 +23606,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23646,11 +23618,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23658,11 +23630,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23672,11 +23644,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23684,11 +23656,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23696,11 +23668,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23708,11 +23680,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23721,11 +23693,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23734,11 +23706,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23748,7 +23720,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23756,69 +23728,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23826,48 +23798,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23878,7 +23850,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23888,17 +23860,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23907,14 +23879,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23925,7 +23897,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23933,30 +23905,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23964,30 +23936,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23995,60 +23967,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24057,79 +24029,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24138,7 +24110,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24146,7 +24118,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24156,21 +24128,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24178,7 +24150,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24187,7 +24159,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24197,14 +24169,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24213,28 +24185,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24243,27 +24215,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24273,7 +24245,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24283,13 +24255,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24509,7 +24481,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24517,7 +24489,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24528,15 +24500,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24544,7 +24516,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24552,7 +24524,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24564,43 +24536,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24609,23 +24581,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/cs/LC_MESSAGES/messages.po b/locales/cs/LC_MESSAGES/messages.po index e7815fd5e..26769ca99 100644 --- a/locales/cs/LC_MESSAGES/messages.po +++ b/locales/cs/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-03-13 10:55+0000\n" "Last-Translator: Luky12568 \n" "Language-Team: Czech `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8563,7 +8563,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8588,79 +8588,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8668,7 +8634,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8677,7 +8643,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13579,7 +13545,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23030,7 +22996,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23502,7 +23468,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23512,28 +23484,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23544,18 +23516,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23563,22 +23535,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23587,11 +23559,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23601,11 +23573,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23615,11 +23587,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23627,11 +23599,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23642,11 +23614,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23654,11 +23626,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23666,11 +23638,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23680,11 +23652,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23692,11 +23664,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23704,11 +23676,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23716,11 +23688,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23729,11 +23701,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23742,11 +23714,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23756,7 +23728,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23764,69 +23736,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23834,48 +23806,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23886,7 +23858,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23896,17 +23868,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23915,14 +23887,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23933,7 +23905,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23941,30 +23913,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23972,30 +23944,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24003,60 +23975,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24065,79 +24037,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24146,7 +24118,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24154,7 +24126,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24164,21 +24136,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24186,7 +24158,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24195,7 +24167,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24205,14 +24177,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24221,28 +24193,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24251,27 +24223,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24281,7 +24253,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24291,13 +24263,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24517,7 +24489,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24525,7 +24497,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24536,15 +24508,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24552,7 +24524,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24560,7 +24532,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24572,43 +24544,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24617,23 +24589,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/de/LC_MESSAGES/messages.po b/locales/de/LC_MESSAGES/messages.po index d21d32a6b..d6ab76e0f 100644 --- a/locales/de/LC_MESSAGES/messages.po +++ b/locales/de/LC_MESSAGES/messages.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-04-26 13:01+0000\n" "Last-Translator: Jean-Luc Tibaux \n" "Language-Team: German `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8861,7 +8861,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8886,80 +8886,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -#, fuzzy -msgid "Signing the distribution packages" -msgstr "Distributionspaket" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8967,7 +8932,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8976,7 +8941,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13879,7 +13844,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23361,7 +23326,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23833,7 +23798,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23843,28 +23814,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23875,18 +23846,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23894,22 +23865,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23918,11 +23889,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23932,11 +23903,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23946,11 +23917,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23958,11 +23929,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23973,11 +23944,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23985,11 +23956,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23997,11 +23968,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -24011,11 +23982,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24023,11 +23994,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -24035,11 +24006,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -24047,11 +24018,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -24060,11 +24031,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24073,11 +24044,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24087,7 +24058,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24095,69 +24066,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24165,48 +24136,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24217,7 +24188,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24227,17 +24198,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24246,14 +24217,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24264,7 +24235,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24272,30 +24243,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24303,30 +24274,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24334,60 +24305,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24396,79 +24367,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24477,7 +24448,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24485,7 +24456,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24495,21 +24466,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24517,7 +24488,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24526,7 +24497,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24536,14 +24507,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24552,28 +24523,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24582,27 +24553,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24612,7 +24583,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24622,13 +24593,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24848,7 +24819,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24856,7 +24827,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24867,15 +24838,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24883,7 +24854,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24891,7 +24862,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24903,43 +24874,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24948,23 +24919,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" @@ -26618,3 +26595,7 @@ msgid "" "recommended to stick with *regular packages* and ``__init__.py`` (even if " "the file is empty)." msgstr "" + +#, fuzzy +#~ msgid "Signing the distribution packages" +#~ msgstr "Distributionspaket" diff --git a/locales/eo/LC_MESSAGES/messages.po b/locales/eo/LC_MESSAGES/messages.po index 391f4e11e..2cfeaf51b 100644 --- a/locales/eo/LC_MESSAGES/messages.po +++ b/locales/eo/LC_MESSAGES/messages.po @@ -8,8 +8,8 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" -"PO-Revision-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" +"PO-Revision-Date: 2025-05-09 17:01+0000\n" "Last-Translator: phlostically \n" "Language-Team: Esperanto \n" @@ -3462,7 +3462,7 @@ msgstr "" "segmenton, sed havas neretrokongruajn ŝanĝojn." #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "Semantika versiado" @@ -5071,7 +5071,7 @@ msgstr "Priskribo" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "Ekzemploj" @@ -10754,12 +10754,14 @@ msgstr "" "`cibuildwheel`." #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +#, fuzzy +#| msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "Starigi fidatan eldonadon" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -10773,7 +10775,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -10908,6 +10910,15 @@ msgid "Defining a workflow job environment" msgstr "Difini laborfluan taskan medion" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:130 +#, fuzzy +#| msgid "" +#| "Now, let's add initial setup for our job that will publish to PyPI. It's " +#| "a process that will execute commands that we'll define later. In this " +#| "guide, we'll use the latest stable Ubuntu LTS version provided by GitHub " +#| "Actions. This also defines a GitHub Environment for the job to run in its " +#| "context and a URL to be displayed in GitHub's UI nicely. Additionally, it " +#| "allows acquiring an OpenID Connect token that the ``pypi-publish`` " +#| "actions needs to implement secretless trusted publishing to PyPI." msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -10915,7 +10926,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" "Nun, ni aldonu komencan agordon por la tasko eldoni al PyPI. Ĝi estas " "procezo, kiu rulos komandojn difinotajn. En ĉi tiu gvidilo, ni uzas la plej " @@ -10952,70 +10963,19 @@ msgstr "" "la distribua pako per la ago `download-artifact`_, ĝi alŝutas la enhavon de " "la dosierujo ``dist/`` al PyPI senkondiĉe." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "Subskribi la distribuajn pakojn" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" -"La jena tasko subskribas la distribuajn pakojn per `Sigstore`_, la sama " -"artefakto-subskriba sistemo `uzata por CPython `_." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" -"Unue, ĝi uzas la `GitHub-ago sigstore/gh-action-sigstore-python `_ por subskribi la distribuajn pakojn. " -"Sekve, ĝi kreas malplenan eldonon ĉe GitHub el la aktuala etikedo per la " -"komandlinia ilo ``gh``. Notu, ke tiu paŝo estas modifebla; vidu la " -"`dokumentaron pri gh release `_." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -"Vi eble devas administri la permesojn de ``GITHUB_TOKEN`` por ŝalti krei la " -"GitHub-eldonon. Vidu `la dokumentaron de GitHub `_ por " -"instrukcioj. Specife, la ĵetono bezonas la permeson ``contents: write``." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "Fine, la subskribitaj distribuoj alŝutiĝas al GitHub Release." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" -"Tio anstataŭigas GPG-subskribon, kiun `PyPI ne plu subtenas `_. Tamen, tiu tasko ne estas deviga " -"kaj estas ellasebla por alŝutado al PyPI." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "Aparta laborfluo por eldoni al TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11023,7 +10983,7 @@ msgstr "" "Nun ripetu tiujn paŝojn, kreante alian taskon por eldonado al la pakindekso " "Prova PyPI sub la sekcio ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11033,20 +10993,20 @@ msgstr "" "necesas, ĉar ĝi laŭfasone ruliĝas post ĉiu enmeto en la ĉefbranĉon kaj ofte " "indikas sanan eldonadan ĉenstablon." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "La plena laborfluo por kontinuaj integrado kaj disponigo" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "Jen alineo pri la plena laborfluo laŭ la ĉi-supra gvidilo." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "Jen fino!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11054,7 +11014,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11063,7 +11023,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -17251,7 +17211,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "Historio" @@ -19881,7 +19841,7 @@ msgstr "Python-ekvivalentaĵo" #: ../source/specifications/dependency-specifiers.rst:249 msgid "Type" -msgstr "" +msgstr "Tipo" #: ../source/specifications/dependency-specifiers.rst:250 msgid "Sample values" @@ -20061,17 +20021,13 @@ msgid "" msgstr "Eraro, se ne ekzistas kunteksto interpretanta la specifon." #: ../source/specifications/dependency-specifiers.rst:302 -#, fuzzy -#| msgid "``pyproject.toml``" msgid "``toml``" -msgstr "``pyproject.toml``" +msgstr "``toml``" #: ../source/specifications/dependency-specifiers.rst:303 #: ../source/specifications/pylock-toml.rst:108 -#, fuzzy -#| msgid "``extra``" msgid "``extras``" -msgstr "``extra``" +msgstr "``extras``" #: ../source/specifications/dependency-specifiers.rst:306 #: ../source/specifications/dependency-specifiers.rst:311 @@ -20080,19 +20036,15 @@ msgstr "" #: ../source/specifications/dependency-specifiers.rst:307 msgid "``{\"toml\"}``" -msgstr "" +msgstr "``{\"toml\"}``" #: ../source/specifications/dependency-specifiers.rst:308 -#, fuzzy -#| msgid "``dependencies``" msgid "``dependency_groups``" -msgstr "``dependencies``" +msgstr "``dependency_groups``" #: ../source/specifications/dependency-specifiers.rst:312 -#, fuzzy -#| msgid "``test``" msgid "``{\"test\"}``" -msgstr "``test``" +msgstr "``{\"test\"}``" #: ../source/specifications/dependency-specifiers.rst:314 msgid "" @@ -23861,10 +23813,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:65 -#, fuzzy -#| msgid "``version``" msgid "``lock-version``" -msgstr "``version``" +msgstr "``lock-version``" #: ../source/specifications/pylock-toml.rst:67 msgid "**Type**: string; value of ``\"1.0\"``" @@ -23909,10 +23859,8 @@ msgid "If a tool doesn't support a major version, it MUST raise an error." msgstr "" #: ../source/specifications/pylock-toml.rst:81 -#, fuzzy -#| msgid "``entry-points``" msgid "``environments``" -msgstr "``entry-points``" +msgstr "``environments``" #: ../source/specifications/pylock-toml.rst:83 #: ../source/specifications/pylock-toml.rst:110 @@ -24035,10 +23983,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:130 -#, fuzzy -#| msgid "The ``[dependency-groups]`` Table" msgid "``dependency-groups``" -msgstr "La Tabelo ``[dependency-groups]``" +msgstr "``dependency-groups``" #: ../source/specifications/pylock-toml.rst:134 #: ../source/specifications/pylock-toml.rst:716 @@ -24069,7 +24015,7 @@ msgstr "" #: ../source/specifications/pylock-toml.rst:152 msgid "``default-groups``" -msgstr "" +msgstr "``default-groups``" #: ../source/specifications/pylock-toml.rst:156 msgid "**Inspiration**: Poetry_, PDM_" @@ -24097,7 +24043,7 @@ msgstr "" #: ../source/specifications/pylock-toml.rst:171 msgid "``created-by``" -msgstr "" +msgstr "``created-by``" #: ../source/specifications/pylock-toml.rst:175 msgid "**Inspiration**: Tools with their name in their lock file name" @@ -24124,10 +24070,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:186 -#, fuzzy -#| msgid "``packages``" msgid "``[[packages]]``" -msgstr "``packages``" +msgstr "``[[packages]]``" #: ../source/specifications/pylock-toml.rst:188 #: ../source/specifications/pylock-toml.rst:254 @@ -24149,10 +24093,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:199 -#, fuzzy -#| msgid "``packages``" msgid "``packages.name``" -msgstr "``packages``" +msgstr "``packages.name``" #: ../source/specifications/pylock-toml.rst:203 msgid "**Inspiration**: :ref:`core-metadata-name`" @@ -24169,10 +24111,8 @@ msgstr "" "komparado." #: ../source/specifications/pylock-toml.rst:210 -#, fuzzy -#| msgid "``packages``" msgid "``packages.version``" -msgstr "``packages``" +msgstr "``packages.version``" #: ../source/specifications/pylock-toml.rst:214 msgid "**Inspiration**: :ref:`core-metadata-version`" @@ -24207,10 +24147,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:227 -#, fuzzy -#| msgid "``packages``" msgid "``packages.marker``" -msgstr "``packages``" +msgstr "``packages.marker``" #: ../source/specifications/pylock-toml.rst:231 msgid "**Inspiration**: PDM_" @@ -24223,10 +24161,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:240 -#, fuzzy -#| msgid "``requires-python``" msgid "``packages.requires-python``" -msgstr "``requires-python``" +msgstr "``packages.requires-python``" #: ../source/specifications/pylock-toml.rst:244 msgid "**Inspiration**: :ref:`core-metadata-requires-python`" @@ -24239,10 +24175,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:252 -#, fuzzy -#| msgid "``dependencies``" msgid "``[[packages.dependencies]]``" -msgstr "``dependencies``" +msgstr "``[[packages.dependencies]]``" #: ../source/specifications/pylock-toml.rst:257 msgid "" @@ -24267,10 +24201,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:272 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.vcs]``" -msgstr "``packages``" +msgstr "``[packages.vcs]``" #: ../source/specifications/pylock-toml.rst:274 #: ../source/specifications/pylock-toml.rst:376 @@ -24323,10 +24255,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:294 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.type``" -msgstr "``packages``" +msgstr "``packages.vcs.type``" #: ../source/specifications/pylock-toml.rst:296 msgid "" @@ -24349,10 +24279,8 @@ msgid "The type of version control system used." msgstr "Instali el versikontrola sistemo" #: ../source/specifications/pylock-toml.rst:306 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.url``" -msgstr "``packages``" +msgstr "``packages.vcs.url``" #: ../source/specifications/pylock-toml.rst:309 msgid "**Required?**: if :ref:`pylock-packages-vcs-path` is not specified" @@ -24365,10 +24293,8 @@ msgid "The URL_ to the source tree." msgstr "La fontarbo" #: ../source/specifications/pylock-toml.rst:317 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.path``" -msgstr "``packages``" +msgstr "``packages.vcs.path``" #: ../source/specifications/pylock-toml.rst:320 msgid "**Required?**: if :ref:`pylock-packages-vcs-url` is not specified" @@ -24392,10 +24318,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:331 -#, fuzzy -#| msgid "``requested_revision`` field" msgid "``packages.vcs.requested-revision``" -msgstr "kampo ``requested_revision``" +msgstr "``packages.vcs.requested-revision``" #: ../source/specifications/pylock-toml.rst:336 msgid "The branch/tag/ref/commit/revision/etc. that the user requested." @@ -24408,10 +24332,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:345 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.commit-id``" -msgstr "``packages``" +msgstr "``packages.vcs.commit-id``" #: ../source/specifications/pylock-toml.rst:350 msgid "The exact commit/revision number that is to be installed." @@ -24437,7 +24359,7 @@ msgstr "" #: ../source/specifications/pylock-toml.rst:359 msgid "``packages.vcs.subdirectory``" -msgstr "" +msgstr "``packages.vcs.subdirectory``" #: ../source/specifications/pylock-toml.rst:363 msgid "**Inspiration**: :ref:`direct-url-data-structure-subdirectories`" @@ -24455,10 +24377,8 @@ msgid "The path MUST be relative to the root of the source tree structure." msgstr "" #: ../source/specifications/pylock-toml.rst:374 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.directory]``" -msgstr "``packages``" +msgstr "``[packages.directory]``" #: ../source/specifications/pylock-toml.rst:377 msgid "" @@ -28851,7 +28771,7 @@ msgstr "" "normigita per :pep:`639`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "Versispecifiloj" @@ -29454,7 +29374,17 @@ msgid "" "releases::" msgstr "Evolua eldono estas ankaŭ permesata por antaŭeldono kaj posteldono::" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +#, fuzzy +#| msgid "" +#| "Developmental releases are also permitted for pre-releases and post-" +#| "releases::" +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "Evolua eldono estas ankaŭ permesata por antaŭeldono kaj posteldono::" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -29464,7 +29394,7 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " @@ -29474,11 +29404,11 @@ msgstr "" "taŭgas por projekto uzanta la posteldonan notacion por plena flega eldono " "eble inkluzivanta ŝanĝojn de kodo." -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "Versiaj epokoj" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" @@ -29486,11 +29416,11 @@ msgstr "" "Se epoko ekzistas en versio-identigilo, ĝi ĉeestas antaŭ ĉiaj aliaj " "komponantoj, apartigite el la eldono-segmento per krisigno::" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "Se la epoko ne estas eksplicita, la implicita epoko estas ``0``." -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -29507,7 +29437,7 @@ msgstr "" "semantikaj versioj kiel ``1.0``, do la novaj eldonoj estus rigardataj kiel " "*pli malnovaj* ol la dato-bazaj eldonoj laŭ la ordinara ordigado::" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " @@ -29516,11 +29446,11 @@ msgstr "" "Tamen, eksplicitante epokon, oni povas ŝanĝi la ordon, ĉar ĉiuj versioj de " "pli posta epoko estas ordigitaj post versioj de pli frua epoko::" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "Normigo" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -29528,11 +29458,11 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "Usklecdistingo" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " @@ -29542,11 +29472,11 @@ msgstr "" "minusklo. Tio permesas version kiel ``1.1RC1``, kies norma formo estas " "``1.1rc1``." -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "Entjera Normigo" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -29560,11 +29490,11 @@ msgstr "" "entjero en alfabetcifera segmento de loka versio kiel ``1.0+foo0100``, kiu " "estas sia propra normigita formo." -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "Antaŭeldonaj apartigiloj" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -29580,11 +29510,11 @@ msgstr "" "specifilo kaj la numero. Tio permesas versiojn kiel ``1.0a.1``, kies norma " "formo estas ``1.0a1``." -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "Literumado de antaŭeldono" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -29599,11 +29529,11 @@ msgstr "" "normigitaj al ``1.1a1``, ``1.1b2`` kaj ``1.1rc3``. Ĉiukaze la ekstra " "literumaĵo ekvivalentas la norman formon." -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "Implicita antaŭeldona numero" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -29614,11 +29544,11 @@ msgstr "" "eksplicas ``0``. Tio permesas versiojn kiel ``1.2a``, kies norma formo estas " "``1.2a0``." -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "Posteldonaj disigiloj" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -29635,11 +29565,11 @@ msgstr "" "apartigilon inter la posteldono-specifilo kaj la numero. Tio permesas " "versiojn kiel ``1.2.post-2``, kies norma formo estas ``1.2.post2``." -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "Posteldona literumado" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -29650,11 +29580,11 @@ msgstr "" "versiojn kiel ``1.0-r4``, kies normigita formo estas ``1.0.post4``. Same " "kiel antaŭeldono, la ekstraj literumaĵoj ekvivalentas la normigitajn formojn." -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "Implicita posteldona numero" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -29665,11 +29595,11 @@ msgstr "" "eksplicas ``0``. Tio permesas versiojn kiel ``1.2post``, kies norma formo " "estas ``1.2post0``." -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "Implicitaj posteldonoj" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -29684,11 +29614,11 @@ msgstr "" "uzi tion kune kun la regulo de implicita posteldona numero. Alivorte, ``1.0-" "`` *ne* validas, kaj ĝia norma formo *ne* estas ``1.0.post0``." -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "Disigiloj de evoluada eldono" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -29700,11 +29630,11 @@ msgstr "" "versiojn kiel ``1.2-dev2`` aŭ ``1.2dev2``, kies norma formo estas " "``1.2dev2``." -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "Implicita evoluada eldona numero" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -29715,11 +29645,11 @@ msgstr "" "formo eksplicas ``0``. Tio permesas versiojn kiel ``1.2.dev``, kies norma " "formo estas ``1.2.dev0``." -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "Lokaj versiaj segmentoj" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -29730,11 +29660,11 @@ msgstr "" "apartigiloj ``-`` kaj ``_``. La norma formo uzas ``.``. Tio permesas " "versiojn kiel ``1.0+ubuntu-1``, kies norma formo estas ``1.0+ubuntu.1``." -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "Prefiksa signo «v»" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -29743,11 +29673,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "Komenca kaj Fina Blanka Spaco" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -29760,11 +29690,11 @@ msgstr "" "``\\n``, ``\\r``, ``\\f``, kaj ``\\v``. Tio permesas racian pritraktadon de " "senintenca blanka spaco, kiel ``1.0\\n``, kiu estas normigita al ``1.0``." -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "Ekzemploj de versiaj skemoj observantaj la regulojn" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -29774,7 +29704,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -29782,21 +29712,21 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "Simpla «maĵora.minora» versiado::" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "Simpla «maĵora.minora.mikroa» versiado::" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" "«maĵora.minora» versiado kun alfa-, beta-, kaj kandidataj antaŭeldonoj::" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" @@ -29804,17 +29734,17 @@ msgstr "" "«maĵora.minora» versiado kun evoluaj eldonoj, eldonkandidatoj kaj " "posteldonoj por malgravaj korektoj::" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "Datobaza eldono, kun alkrementata numero en ĉiu jaro, sen nulo::" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "Resumo pri permesataj sufiksoj kaj relativa ordo" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " @@ -29824,7 +29754,7 @@ msgstr "" "distribuajn metadatenojn, ne aŭtoroj de Python-distribuoj elektantaj versian " "skemon." -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " @@ -29834,7 +29764,7 @@ msgstr "" "valoro de la epoko. Se epoka segmento mankas, la implicita nombra valoro " "estas ``0``." -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " @@ -29844,7 +29774,7 @@ msgstr "" "ordo de opoj en Python, kiam la normigita eldona segmento estas analizita " "jene::" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." @@ -29852,7 +29782,7 @@ msgstr "" "Ĉiuj eldono-segmentoj pri la komparo DEVAS esti samlongigitaj, metante " "nulojn antaŭ pli mallongaj segmentoj laŭbezone." -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" @@ -29860,7 +29790,7 @@ msgstr "" "Ene de numera eldono (``1.0``, ``2.7.3``), la ĉi-subaj sufiksoj estas " "permesataj kaj DEVAS esti ordigitaj jene::" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -29872,7 +29802,7 @@ msgstr "" "kaj ``rc`` en la sama eldonsegmento pro ambigueco kaj tamen observi la " "specifon." -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " @@ -29882,7 +29812,7 @@ msgstr "" "``1.0c1``), la ĉi-subaj sufiksoj estas permesataj kaj DEVAS esti ordigitaj " "jene::" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" @@ -29890,7 +29820,7 @@ msgstr "" "Ene de posteldono (``1.0.post1``), la jenaj sufiksoj estas permesataj kaj " "DEVAS esti ordigitaj jene::" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." @@ -29899,7 +29829,7 @@ msgstr "" "Notu, ke ``devN`` kaj ``postN`` DEVAS esti antaŭita de punkto, eĉ tuj post " "numera versio (ekz. ``1.0.dev456``, ``1.0.post1``)." -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." @@ -29907,15 +29837,15 @@ msgstr "" "En antaŭeldona, posteldona aŭ evoluada-eldona segmento kun komuna prefikso, " "ordigado DEVAS esti laŭ la valoro de la numera komponanto." -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "Jen ekzemplo de multaj eblaj kombinaĵoj::" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "Ordigo de versioj trans diversaj metadatenaj versioj" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" @@ -29925,7 +29855,7 @@ msgstr "" "norman skemon pri identigado kaj ordigado de versioj. Tamen Metadatenoj v1.2 " "(:pep:`345`) ja specifas skemon difinitan en :pep:`386`." -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -29942,7 +29872,7 @@ msgstr "" "version. Tiaj postuloj necesigas normigadon al unu sintaksanaliza meĥanismo " "uzenda por ĉiuj versioj de projekto." -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -29952,7 +29882,7 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." @@ -29960,11 +29890,11 @@ msgstr "" "Uzanto de distribuo povas deziri eksplicite forigi nekongruajn versiojn el " "sia privata pakindekso." -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "Kongrueco kun aliaj versiaj skemoj" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -29977,7 +29907,7 @@ msgstr "" "projekto-specifa versio povas esti konservita en la metadatenoj, dum la " "tradukita publika versio estas en la versia kampo." -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " @@ -29986,7 +29916,7 @@ msgstr "" "Tiu permesas al aŭtomata distribuilo ĝuste ordigi eldonojn dum aŭtoroj povas " "uzi sian preferatan versian skemon por siaj projektoj." -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -30002,7 +29932,7 @@ msgstr "" "indas kompreni ĝin, ĉar ĝi diskutas multajn problemojn pri dependado de " "aliaj distribuoj kaj pri eldonado de distribuo, de kiu aliaj dependas." -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -30014,7 +29944,7 @@ msgstr "" "kongruas kun la versia skemo en ĉi tiu specifo, kaj ni rekomendas observi " "tian aspekton." -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " @@ -30024,7 +29954,7 @@ msgstr "" "plusosigno (konstruoj – paragrafo 11) *ne* observas ĉi tiun specifon kaj " "estas malpermesata en la publika versia kampo." -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " @@ -30034,18 +29964,18 @@ msgstr "" "kongrua publika versio estas uzi la sufikson ``.devN`` por specifi la taŭgan " "versian ordon." -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" "Specifaj konstruaj informoj povas ankaŭ esti inkluzivitaj en lokaj versiaj " "etikedoj." -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "Versiaj etikedoj per distribuita versikontrola sistemo" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -30057,7 +29987,7 @@ msgstr "" "oni ne povas fidinde ordigi haketaĵojn, oni ne permesas tiajn versiojn en la " "publika versio-kampo." -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " @@ -30067,17 +29997,17 @@ msgstr "" "identigas tiajn eldonojn publike, dum la originala versikontrolsistema " "etikedo povas esti unu el la projektaj metadatenoj." -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" "Loka versia etikedo ankaŭ povas inkluzivi identigan haketaĵan informon." -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "Versiado laŭ Olson-datenbanko" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " @@ -30087,7 +30017,7 @@ msgstr "" "horzono-datenbanko Olson: la jaron, sekvitan de minuskla litero de la versio " "de la datenbanko en tiu jaro." -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -30098,7 +30028,7 @@ msgstr "" "``, en kiu la numero komenciĝas ĉe nulo aŭ unuo (por la eldono " "``a``) kaj alkrementiĝas por ĉiu sekva datenbanka ĝisdatigo en la jaro." -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." @@ -30106,7 +30036,7 @@ msgstr "" "Samkiel aliaj tradukitaj versiaj identigiloj, la respondanta versio de la " "Olson-datenbanko povas esti registrita en la projektaj metadatenoj." -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" @@ -30114,39 +30044,39 @@ msgstr "" "Versi-specifilo konsistas el serio de versio-kondiĉoj apartigitaj per komoj. " "Ekzemple::" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "La kompara operatoro determinas la specon de versia kondiĉo:" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: Kondiĉo `Kongrua eldono `_" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "``==``: Kondiĉo `Versia egaleco `_" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: Kondiĉo `Ekskluzivo de versio `_" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" "``<=``, ``>=``: Kondiĉo `Inkluziva orda komparo `_" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" "``<``, ``>``: Kondiĉo `Ekskluziva orda komparo `_" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: Kondiĉo `Arbitra egaleco `_." -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " @@ -30156,7 +30086,7 @@ msgstr "" "devas kongrui kun ĉiuj donitaj versio-kondiĉoj por kongrui kun la tuta " "specifilo." -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." @@ -30164,7 +30094,7 @@ msgstr "" "Blanka spaco inter kondiĉa operatoro kaj la sekva versia identigilo estas " "nedeviga; same pri la blanka spaco ĉirkaŭ komo." -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -30173,7 +30103,7 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " @@ -30183,11 +30113,11 @@ msgstr "" "esti uzata en versio-specifilo, kaj oni DEVAS plene ignori lokan versian " "etikedon dum kontrolado ĉu kandidata versio kongruas kun iu versio-specifilo." -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "Kongrua eldono" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " @@ -30197,7 +30127,7 @@ msgstr "" "kaj versio-identigilo. Ĝi kongruas kun kandidata versio atendate kongrua kun " "la specifita versio." -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " @@ -30207,7 +30137,7 @@ msgstr "" "skemo `_. Loka versio-identigilo estas MALPERMESATA en ĉi " "tiu versio-specifilo." -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" @@ -30215,7 +30145,7 @@ msgstr "" "Por iu eldono-specifilo ``V.N``, la kondiĉo pri kongrua eldono estas " "proksimume ekvivalenta al la jena paro de kondiĉoj::" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." @@ -30223,11 +30153,11 @@ msgstr "" "Oni DEVAS NE uzi ĉi tiun operatoron kun unusegmenta versia numero kiel " "``~=1``." -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "Ekzemple, la jenaj grupoj de versio-kondiĉoj estas ekvivalentaj::" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " @@ -30237,7 +30167,7 @@ msgstr "" "kongrua eldono kiel ``V.N.sufikso``, do la sufikso estas ignorita dum " "determinado de la postulata prefiksa kongrueco::" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " @@ -30247,11 +30177,11 @@ msgstr "" "la supozata grado de kongrueco en kondiĉo pri kongruaj eldonoj estas " "modifebla per nuloj ĉe la komenco de la versio-specifilo::" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "Versia egaleco" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." @@ -30259,7 +30189,7 @@ msgstr "" "Versio-egaleca kondiĉo inkluzivas la versio-egalecan operatoron ``==`` kaj " "versian identigilon." -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " @@ -30269,7 +30199,7 @@ msgstr "" "en `Versia skemo `_, sed sufiksa ``.*`` estas permesata post " "publika versio-identigilo jene." -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -30278,7 +30208,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -30289,7 +30219,7 @@ msgstr "" "versio-specifilo. Aŭtomata ilo almenaŭ AVERTU pri maltaŭga strikta versio-" "egaleco kaj POVAS malakcepti ĝin." -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -30299,8 +30229,8 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" @@ -30308,7 +30238,7 @@ msgstr "" "Ekzemple, pri la versio ``1.1.post1``, la ĉi-subaj kondiĉoj estas plenumitaj " "aŭ ne jene::" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " @@ -30318,7 +30248,7 @@ msgstr "" "prefiksan ``.``. Tial, pri la versio ``1.1a1``, kaj jenaj kondiĉoj kongruus " "aŭ ne kongruus jene::" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -30329,7 +30259,7 @@ msgstr "" "konsekvenco de la nulo-antaŭmeta regulo pri la eldonsegmento de versio-" "identigilo). Pri la versio ``1.1``, la jenaj kondiĉoj kongruus aŭ ne jene::" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -30338,7 +30268,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -30348,7 +30278,7 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " @@ -30358,7 +30288,7 @@ msgstr "" "versio-etikedo), do la loka versio-etikedo de iu ajn kandidata versio DEVAS " "ignoriĝi dum komputado de kongrueco inter versioj." -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -30367,11 +30297,11 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "Ekskluzivo de versio" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." @@ -30379,7 +30309,7 @@ msgstr "" "Versi-ekskluzivada kondiĉo konsistas el la versio-ekskluzivada operatoro ``!" "=`` kaj versia identigilo." -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " @@ -30389,11 +30319,11 @@ msgstr "" "kiel tiuj de la operatoro de `Versia egaleco `_, krom ke " "la senco de kongrueco estas mala." -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "Inkluziva ordita komparo" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -30402,12 +30332,12 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "La operatoroj de inkluziva orda komparo estas ``<=`` kaj ``>=``." -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." @@ -30416,16 +30346,16 @@ msgstr "" "nuloj, kiom necesas por certigi, ke la eldonsegmentoj kompariĝas je la sama " "longo." -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "Loka versia identigilo NE estas permesata en ĉi tiu versispecifilo." -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "Ekskluziva ordita komparo" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -30435,7 +30365,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -30450,7 +30380,7 @@ msgstr "" "postN``. Ekzemple, ``>1.7`` permesas ``1.7.1`` sed ne ``1.7.0.post1``; " "``>1.7.post2`` permesas ``1.7.1`` kaj ``1.7.0.post3`` sed ne ``1.7.0``." -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." @@ -30458,7 +30388,7 @@ msgstr "" "La ekskluziva orda komparo ``>V`` **DEVAS NE** kongrui kun loka versio de la " "specifita versio." -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " @@ -30722,7 +30652,7 @@ msgstr "" "haketaĵan valoron inkluzivante eron ``=`` kiel parton de la URL-fragmento." -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -30731,7 +30661,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -30743,7 +30673,7 @@ msgstr "" "fino de la retadreso laŭ la notacio ``@`` aŭ " "``@#``." -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -30760,15 +30690,15 @@ msgstr "" "inkluzivu haketaĵon por malhelpi falsadon (estas facile krei fideponejon kun " "iu deponejo; estas malpli facile krei fideponejon kun specifa *haketaĵo*)." -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "Ekzemploj de foraj retadresoj::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "Dosieraj retadresoj" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -30780,7 +30710,7 @@ msgstr "" "```` mankas, la tria suprenstreko DEVAS tamen ekzisti. La " "```` difinas la dosierlokan vojon ĉe la dosiersistemo atingota." -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -30792,7 +30722,7 @@ msgstr "" "nomregno (FQDN), kiu egalas la gastiganton de la aktuala maŝino. Alivorte, " "sur Unikso, la skemo ``file://`` nur povas atingi vojojn ĉe la loka maŝino." -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -30812,11 +30742,11 @@ msgstr "" "org/web/20130321051043/http://blogs.msdn.com/b/ie/archive/2006/12/06/file-" "uris-in-windows.aspx>`_." -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "Resumo pri diferencoj de pkg_resources.parse_version" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " @@ -30826,7 +30756,7 @@ msgstr "" "estis verkita. Post la aprobo de la PEP, setuptools 6.0 kaj postaj versioj " "adoptis la konduton priskribitan ĉi tie." -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " @@ -30836,7 +30766,7 @@ msgstr "" "versio estu pli granda ol la sama versio sen loka versio, dum " "``pkg_resources.parse_version`` konsideras ĝin kiel markon de antaŭeldono." -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " @@ -30845,7 +30775,7 @@ msgstr "" "Ĉiu tiu specifo intence restriktas la sintakson de valida versio, dum " "``pkg_resources.parse_version`` provas analizi *iun ajn* signoĉenon." -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " @@ -30855,11 +30785,11 @@ msgstr "" "``1.0.dev1.post1.dev5``. Ĉi tiu specifo, tamen, nur permesas nur unu uzon de " "ĉiu tipo, en difinita ordo." -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "Apendico: Sintaksanalizi versian tekston per regulaj esprimoj" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -30868,7 +30798,7 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" @@ -30876,7 +30806,7 @@ msgstr "" "Por kontroli, ĉu versia identigilo estas en la kanona formo, oni povas uzi " "la jenan funkcion:" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_):" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "Aŭgusto 2014: Ĉi tiu specifo estis aprobita per :pep:`440`." +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "Virtualaj Python-Medioj" @@ -33020,6 +32956,61 @@ msgstr "" "komencanto pri Python-pakado, recomendate estas nur uzi *ordinarajn pakojn* " "kaj ``__init__.py`` (eĉ se tiu dosiero estas malplena)." +#~ msgid "Signing the distribution packages" +#~ msgstr "Subskribi la distribuajn pakojn" + +#~ msgid "" +#~ "The following job signs the distribution packages with `Sigstore`_, the " +#~ "same artifact signing system `used to sign CPython `_." +#~ msgstr "" +#~ "La jena tasko subskribas la distribuajn pakojn per `Sigstore`_, la sama " +#~ "artefakto-subskriba sistemo `uzata por CPython `_." + +#~ msgid "" +#~ "Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ " +#~ "to sign the distribution packages. In the next step, an empty GitHub " +#~ "Release from the current tag is created using the ``gh`` CLI. Note this " +#~ "step can be further customised. See the `gh release documentation " +#~ "`_ as a reference." +#~ msgstr "" +#~ "Unue, ĝi uzas la `GitHub-ago sigstore/gh-action-sigstore-python `_ por subskribi la distribuajn " +#~ "pakojn. Sekve, ĝi kreas malplenan eldonon ĉe GitHub el la aktuala etikedo " +#~ "per la komandlinia ilo ``gh``. Notu, ke tiu paŝo estas modifebla; vidu la " +#~ "`dokumentaron pri gh release `_." + +#~ msgid "" +#~ "You may need to manage your ``GITHUB_TOKEN`` permissions to enable " +#~ "creating the GitHub Release. See the `GitHub documentation `_ for " +#~ "instructions. Specifically, the token needs the ``contents: write`` " +#~ "permission." +#~ msgstr "" +#~ "Vi eble devas administri la permesojn de ``GITHUB_TOKEN`` por ŝalti krei " +#~ "la GitHub-eldonon. Vidu `la dokumentaron de GitHub `_ por " +#~ "instrukcioj. Specife, la ĵetono bezonas la permeson ``contents: write``." + +#~ msgid "" +#~ "Finally, the signed distributions are uploaded to the GitHub Release." +#~ msgstr "Fine, la subskribitaj distribuoj alŝutiĝas al GitHub Release." + +#~ msgid "" +#~ "This is a replacement for GPG signatures, for which support has been " +#~ "`removed from PyPI `_. However, this job is not mandatory for uploading to PyPI and can be " +#~ "omitted." +#~ msgstr "" +#~ "Tio anstataŭigas GPG-subskribon, kiun `PyPI ne plu subtenas `_. Tamen, tiu tasko ne estas " +#~ "deviga kaj estas ellasebla por alŝutado al PyPI." + #~ msgid "" #~ ":download:`https://packaging.python.org/en/latest/specifications/schemas/" #~ "build-details-v1.0.schema.json <../schemas/build-details-v1.0.schema." diff --git a/locales/es/LC_MESSAGES/messages.po b/locales/es/LC_MESSAGES/messages.po index 4360e65e5..0990bfd9c 100644 --- a/locales/es/LC_MESSAGES/messages.po +++ b/locales/es/LC_MESSAGES/messages.po @@ -17,7 +17,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-05-01 09:08+0000\n" "Last-Translator: Joseph Hale \n" "Language-Team: Spanish `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8958,7 +8958,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8983,80 +8983,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -#, fuzzy -msgid "Signing the distribution packages" -msgstr "Paquete de Distribución" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9064,7 +9029,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9073,7 +9038,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -14008,7 +13973,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23573,7 +23538,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -24047,7 +24012,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -24057,29 +24028,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -24090,19 +24061,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "Traducciones" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -24110,23 +24081,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "Traducciones" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -24135,11 +24106,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -24149,11 +24120,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -24163,11 +24134,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24175,11 +24146,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -24190,11 +24161,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -24202,11 +24173,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24214,11 +24185,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -24228,11 +24199,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24240,11 +24211,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -24252,11 +24223,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -24264,11 +24235,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -24277,11 +24248,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24290,11 +24261,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24304,7 +24275,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24312,69 +24283,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24382,48 +24353,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24434,7 +24405,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24444,17 +24415,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24463,14 +24434,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24481,7 +24452,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24489,30 +24460,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24520,30 +24491,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24551,60 +24522,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24613,80 +24584,80 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 #, fuzzy msgid "Version matching" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24695,7 +24666,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24703,7 +24674,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24713,21 +24684,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24735,7 +24706,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24744,7 +24715,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24754,14 +24725,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24770,29 +24741,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24801,27 +24772,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24831,7 +24802,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24841,13 +24812,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -25067,7 +25038,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -25075,7 +25046,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -25086,16 +25057,16 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 #, fuzzy msgid "Remote URL examples::" msgstr "Por ejemplo::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -25103,7 +25074,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -25111,7 +25082,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -25123,43 +25094,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -25168,23 +25139,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 #, fuzzy msgid "Python Virtual Environments" @@ -26858,6 +26835,10 @@ msgid "" "the file is empty)." msgstr "" +#, fuzzy +#~ msgid "Signing the distribution packages" +#~ msgstr "Paquete de Distribución" + #, fuzzy #~ msgid "Examples:" #~ msgstr "Ejemplos" diff --git a/locales/fa/LC_MESSAGES/messages.po b/locales/fa/LC_MESSAGES/messages.po index b9fb6f6c5..6a2743abf 100644 --- a/locales/fa/LC_MESSAGES/messages.po +++ b/locales/fa/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2023-02-15 07:52+0000\n" "Last-Translator: Arsalan Dehghani \n" "Language-Team: Persian `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8575,7 +8575,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8600,79 +8600,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8680,7 +8646,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8689,7 +8655,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13597,7 +13563,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23069,7 +23035,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23544,7 +23510,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23554,29 +23526,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23587,19 +23559,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23607,23 +23579,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23632,11 +23604,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23646,11 +23618,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23660,11 +23632,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23672,11 +23644,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23687,11 +23659,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23699,11 +23671,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23711,11 +23683,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23725,11 +23697,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23737,11 +23709,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23749,11 +23721,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23761,11 +23733,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23774,11 +23746,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23787,11 +23759,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23801,7 +23773,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23809,69 +23781,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23879,48 +23851,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23931,7 +23903,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23941,17 +23913,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23960,14 +23932,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23978,7 +23950,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23986,30 +23958,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24017,30 +23989,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24048,60 +24020,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24110,79 +24082,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24191,7 +24163,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24199,7 +24171,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24209,21 +24181,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24231,7 +24203,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24240,7 +24212,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24250,14 +24222,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24266,29 +24238,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24297,27 +24269,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24327,7 +24299,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24337,13 +24309,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24563,7 +24535,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24571,7 +24543,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24582,15 +24554,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24598,7 +24570,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24606,7 +24578,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24618,43 +24590,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24663,23 +24635,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/fil/LC_MESSAGES/messages.po b/locales/fil/LC_MESSAGES/messages.po index 6e0f292cd..b2bfef921 100644 --- a/locales/fil/LC_MESSAGES/messages.po +++ b/locales/fil/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2022-11-19 08:28+0000\n" "Last-Translator: RedFurrFox \n" "Language-Team: Filipino `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8561,7 +8561,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8586,79 +8586,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8666,7 +8632,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8675,7 +8641,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13577,7 +13543,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23028,7 +22994,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23500,7 +23466,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23510,28 +23482,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23542,18 +23514,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23561,22 +23533,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23585,11 +23557,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23599,11 +23571,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23613,11 +23585,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23625,11 +23597,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23640,11 +23612,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23652,11 +23624,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23664,11 +23636,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23678,11 +23650,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23690,11 +23662,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23702,11 +23674,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23714,11 +23686,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23727,11 +23699,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23740,11 +23712,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23754,7 +23726,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23762,69 +23734,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23832,48 +23804,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23884,7 +23856,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23894,17 +23866,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23913,14 +23885,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23931,7 +23903,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23939,30 +23911,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23970,30 +23942,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24001,60 +23973,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24063,79 +24035,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24144,7 +24116,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24152,7 +24124,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24162,21 +24134,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24184,7 +24156,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24193,7 +24165,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24203,14 +24175,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24219,28 +24191,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24249,27 +24221,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24279,7 +24251,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24289,13 +24261,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24515,7 +24487,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24523,7 +24495,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24534,15 +24506,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24550,7 +24522,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24558,7 +24530,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24570,43 +24542,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24615,23 +24587,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/fr/LC_MESSAGES/messages.po b/locales/fr/LC_MESSAGES/messages.po index fcd735076..224bd3566 100644 --- a/locales/fr/LC_MESSAGES/messages.po +++ b/locales/fr/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-02-17 11:31+0000\n" "Last-Translator: Bruno Alla \n" "Language-Team: French `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8797,7 +8799,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8822,80 +8824,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -#, fuzzy -msgid "Signing the distribution packages" -msgstr "Paqueter et distribuer des projets" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8903,7 +8870,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8912,7 +8879,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13968,7 +13935,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "Historique" @@ -23657,7 +23624,7 @@ msgstr "" "`241`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -24133,7 +24100,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -24143,29 +24116,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -24176,19 +24149,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -24196,23 +24169,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -24221,11 +24194,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -24235,11 +24208,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -24249,11 +24222,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24261,11 +24234,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -24276,11 +24249,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -24288,11 +24261,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24300,11 +24273,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -24314,11 +24287,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24326,11 +24299,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -24338,11 +24311,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -24350,11 +24323,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -24363,11 +24336,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24376,11 +24349,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24390,7 +24363,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24398,69 +24371,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24468,48 +24441,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24520,7 +24493,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24530,17 +24503,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24549,14 +24522,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24567,7 +24540,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24575,30 +24548,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24606,30 +24579,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24637,60 +24610,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24699,79 +24672,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24780,7 +24753,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24788,7 +24761,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24798,21 +24771,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24820,7 +24793,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24829,7 +24802,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24839,14 +24812,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24855,29 +24828,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24886,27 +24859,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24916,7 +24889,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24926,13 +24899,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -25153,7 +25126,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -25161,7 +25134,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -25172,16 +25145,16 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 #, fuzzy msgid "Remote URL examples::" msgstr "Exemples" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -25189,7 +25162,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -25197,7 +25170,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -25209,43 +25182,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -25254,23 +25227,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 #, fuzzy msgid "Python Virtual Environments" @@ -26932,6 +26911,10 @@ msgid "" "the file is empty)." msgstr "" +#, fuzzy +#~ msgid "Signing the distribution packages" +#~ msgstr "Paqueter et distribuer des projets" + #, fuzzy #~ msgid "Additional file information" #~ msgstr "Outils supplémentaires" diff --git a/locales/frc/LC_MESSAGES/messages.po b/locales/frc/LC_MESSAGES/messages.po index 44be9c3c0..3e1470a7d 100644 --- a/locales/frc/LC_MESSAGES/messages.po +++ b/locales/frc/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2713,7 +2713,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "" @@ -3940,7 +3940,7 @@ msgstr "" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "" @@ -8417,12 +8417,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -8436,7 +8436,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8555,7 +8555,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8580,79 +8580,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8660,7 +8626,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8669,7 +8635,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13571,7 +13537,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23022,7 +22988,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23494,7 +23460,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23504,28 +23476,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23536,18 +23508,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23555,22 +23527,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23579,11 +23551,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23593,11 +23565,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23607,11 +23579,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23619,11 +23591,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23634,11 +23606,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23646,11 +23618,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23658,11 +23630,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23672,11 +23644,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23684,11 +23656,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23696,11 +23668,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23708,11 +23680,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23721,11 +23693,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23734,11 +23706,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23748,7 +23720,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23756,69 +23728,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23826,48 +23798,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23878,7 +23850,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23888,17 +23860,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23907,14 +23879,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23925,7 +23897,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23933,30 +23905,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23964,30 +23936,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23995,60 +23967,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24057,79 +24029,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24138,7 +24110,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24146,7 +24118,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24156,21 +24128,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24178,7 +24150,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24187,7 +24159,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24197,14 +24169,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24213,28 +24185,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24243,27 +24215,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24273,7 +24245,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24283,13 +24255,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24509,7 +24481,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24517,7 +24489,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24528,15 +24500,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24544,7 +24516,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24552,7 +24524,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24564,43 +24536,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24609,23 +24581,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/gl/LC_MESSAGES/messages.po b/locales/gl/LC_MESSAGES/messages.po index f51128137..e1dcc63a5 100644 --- a/locales/gl/LC_MESSAGES/messages.po +++ b/locales/gl/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2713,7 +2713,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "" @@ -3940,7 +3940,7 @@ msgstr "" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "" @@ -8417,12 +8417,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -8436,7 +8436,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8555,7 +8555,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8580,79 +8580,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8660,7 +8626,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8669,7 +8635,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13571,7 +13537,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23022,7 +22988,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23494,7 +23460,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23504,28 +23476,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23536,18 +23508,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23555,22 +23527,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23579,11 +23551,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23593,11 +23565,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23607,11 +23579,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23619,11 +23591,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23634,11 +23606,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23646,11 +23618,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23658,11 +23630,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23672,11 +23644,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23684,11 +23656,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23696,11 +23668,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23708,11 +23680,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23721,11 +23693,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23734,11 +23706,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23748,7 +23720,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23756,69 +23728,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23826,48 +23798,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23878,7 +23850,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23888,17 +23860,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23907,14 +23879,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23925,7 +23897,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23933,30 +23905,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23964,30 +23936,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23995,60 +23967,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24057,79 +24029,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24138,7 +24110,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24146,7 +24118,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24156,21 +24128,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24178,7 +24150,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24187,7 +24159,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24197,14 +24169,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24213,28 +24185,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24243,27 +24215,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24273,7 +24245,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24283,13 +24255,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24509,7 +24481,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24517,7 +24489,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24528,15 +24500,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24544,7 +24516,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24552,7 +24524,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24564,43 +24536,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24609,23 +24581,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/gmh/LC_MESSAGES/messages.po b/locales/gmh/LC_MESSAGES/messages.po index 6179b31ac..253befe1f 100644 --- a/locales/gmh/LC_MESSAGES/messages.po +++ b/locales/gmh/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2713,7 +2713,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "" @@ -3940,7 +3940,7 @@ msgstr "" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "" @@ -8417,12 +8417,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -8436,7 +8436,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8555,7 +8555,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8580,79 +8580,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8660,7 +8626,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8669,7 +8635,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13571,7 +13537,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23022,7 +22988,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23494,7 +23460,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23504,28 +23476,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23536,18 +23508,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23555,22 +23527,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23579,11 +23551,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23593,11 +23565,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23607,11 +23579,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23619,11 +23591,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23634,11 +23606,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23646,11 +23618,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23658,11 +23630,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23672,11 +23644,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23684,11 +23656,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23696,11 +23668,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23708,11 +23680,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23721,11 +23693,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23734,11 +23706,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23748,7 +23720,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23756,69 +23728,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23826,48 +23798,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23878,7 +23850,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23888,17 +23860,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23907,14 +23879,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23925,7 +23897,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23933,30 +23905,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23964,30 +23936,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23995,60 +23967,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24057,79 +24029,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24138,7 +24110,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24146,7 +24118,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24156,21 +24128,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24178,7 +24150,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24187,7 +24159,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24197,14 +24169,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24213,28 +24185,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24243,27 +24215,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24273,7 +24245,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24283,13 +24255,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24509,7 +24481,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24517,7 +24489,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24528,15 +24500,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24544,7 +24516,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24552,7 +24524,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24564,43 +24536,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24609,23 +24581,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/hi/LC_MESSAGES/messages.po b/locales/hi/LC_MESSAGES/messages.po index ddee5b677..c56d9319e 100644 --- a/locales/hi/LC_MESSAGES/messages.po +++ b/locales/hi/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-09-16 10:09+0000\n" "Last-Translator: kumar Shivam \n" "Language-Team: Hindi `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8609,7 +8609,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8634,79 +8634,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8714,7 +8680,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8723,7 +8689,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13629,7 +13595,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23105,7 +23071,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23577,7 +23543,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23587,28 +23559,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23619,18 +23591,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23638,22 +23610,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23662,11 +23634,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23676,11 +23648,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23690,11 +23662,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23702,11 +23674,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23717,11 +23689,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23729,11 +23701,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23741,11 +23713,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23755,11 +23727,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23767,11 +23739,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23779,11 +23751,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23791,11 +23763,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23804,11 +23776,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23817,11 +23789,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23831,7 +23803,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23839,69 +23811,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23909,48 +23881,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23961,7 +23933,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23971,17 +23943,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23990,14 +23962,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24008,7 +23980,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24016,30 +23988,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24047,30 +24019,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24078,60 +24050,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24140,79 +24112,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24221,7 +24193,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24229,7 +24201,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24239,21 +24211,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24261,7 +24233,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24270,7 +24242,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24280,14 +24252,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24296,28 +24268,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24326,27 +24298,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24356,7 +24328,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24366,13 +24338,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24592,7 +24564,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24600,7 +24572,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24611,15 +24583,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24627,7 +24599,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24635,7 +24607,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24647,43 +24619,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24692,23 +24664,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/id/LC_MESSAGES/messages.po b/locales/id/LC_MESSAGES/messages.po index 3ea68c029..f86231f58 100644 --- a/locales/id/LC_MESSAGES/messages.po +++ b/locales/id/LC_MESSAGES/messages.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-10-17 21:16+0000\n" "Last-Translator: oon arfiandwi \n" "Language-Team: Indonesian `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8611,7 +8611,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8636,79 +8636,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8716,7 +8682,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8725,7 +8691,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13633,7 +13599,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23109,7 +23075,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23584,7 +23550,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23594,29 +23566,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23627,19 +23599,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23647,23 +23619,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23672,11 +23644,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23686,11 +23658,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23700,11 +23672,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23712,11 +23684,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23727,11 +23699,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23739,11 +23711,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23751,11 +23723,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23765,11 +23737,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23777,11 +23749,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23789,11 +23761,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23801,11 +23773,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23814,11 +23786,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23827,11 +23799,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23841,7 +23813,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23849,69 +23821,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23919,48 +23891,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23971,7 +23943,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23981,17 +23953,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24000,14 +23972,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24018,7 +23990,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24026,30 +23998,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24057,30 +24029,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24088,60 +24060,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24150,79 +24122,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24231,7 +24203,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24239,7 +24211,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24249,21 +24221,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24271,7 +24243,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24280,7 +24252,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24290,14 +24262,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24306,29 +24278,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24337,27 +24309,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24367,7 +24339,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24377,13 +24349,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24603,7 +24575,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24611,7 +24583,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24622,15 +24594,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24638,7 +24610,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24646,7 +24618,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24658,43 +24630,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24703,23 +24675,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/ja/LC_MESSAGES/messages.po b/locales/ja/LC_MESSAGES/messages.po index 9adcb9bf8..4424cdd43 100644 --- a/locales/ja/LC_MESSAGES/messages.po +++ b/locales/ja/LC_MESSAGES/messages.po @@ -10,8 +10,8 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" -"PO-Revision-Date: 2025-05-03 16:03+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" +"PO-Revision-Date: 2025-05-15 01:03+0000\n" "Last-Translator: moto kawasaki \n" "Language-Team: Japanese \n" @@ -1595,12 +1595,21 @@ msgid "" "anything from library loading errors, to subtle runtime bugs, to " "catastrophic failures (like suddenly crashing and losing data)." msgstr "" +"静的なリンキングとベンダーリングによって、同一ライブラリの複数の異なるバー" +"ジョンが同じプロセスの中でロードされ得ます (例えば、同じライブラリの別バー" +"ジョンにリンクしたふたつの Python パッケージを import しようと試みた場合) 。" +"ある時には、事件にならずに動作しますが、ライブラリのローディングエラーに起因" +"する問題や、微妙な動作中のバグや、 (突然クラッシュしてデータを失うといった) " +"壊滅的な失敗へと至ることもあり得ます。" #: ../source/discussions/downstream-packaging.rst:273 msgid "" "Last but not least, static linking and vendoring results in duplication, and " "may increase the use of both disk space and memory." msgstr "" +"最後ではあるが最も軽微といういうわけではありませんが、静的なリンキングとベン" +"ダーリングの結果として重複が起きて、ディスクスペースとメモリの両方を余計に使" +"うことになります。" #: ../source/discussions/downstream-packaging.rst:279 msgid "" @@ -1610,6 +1619,12 @@ msgid "" "for each dependency, and a general switch to control the default for them, e." "g. via a ``USE_SYSTEM_DEPS`` environment variable." msgstr "" +"双方のニーズの間の良い妥協点は、ベンダード (訳註：パッケージ側が準備したもの" +"の意か) のものを使うかシステムの依存関係を使うかを切り替えるスイッチを提供す" +"ることです。理想的には、パッケージ側が複数の独自の依存関係を持つならば、それ" +"ぞれの依存関係について独立したスイッチを提供するべきで、かつ、例えば " +"``USE_SYSTEM_DEPS`` 環境変数のようにデフォルト設定を制御する一般的なスイッチ" +"をも持つべきです。" #: ../source/discussions/downstream-packaging.rst:285 msgid "" @@ -1619,6 +1634,11 @@ msgid "" "the opportunity to notice their mistake and a chance to consciously decide " "how to solve it." msgstr "" +"ユーザがシステム側の依存関係を使うことを要求していて、特定の依存関係が存在し" +"ないか非互換である場合には、ビルドは、ベンダードのバージョンにフォールバック" +"するよりも説明的なメッセージと共に失敗するべきです。これによって、パッケージ" +"製作者が誤りに気付き、どのように解決するかを意識して解決する機会を得ることが" +"できます。" #: ../source/discussions/downstream-packaging.rst:291 msgid "" @@ -1628,10 +1648,17 @@ msgid "" "projects and downstream repackagers, not to suggest upstream projects take " "on tasks that downstream repackagers are better equipped to handle." msgstr "" +"アップストリーム側プロジェクトが、システム側の依存関係を使ってビルドする *テ" +"スト* をダウンストリーム側の再パッケージ作業者に残しておくことは合理的です。" +"これらのガイドラインのゴールは、アップストリーム側プロジェクトとダウンスト" +"リーム側再パッケージ作業者の間の協調作業がより効率的になるようにお膳立てする" +"ことであって、ダウンストリーム側再パッケージ作業者がよりよく取り扱えるように" +"装備を整えるというタスクをアップストリーム側プロジェクトが分担するようにと示" +"唆するものではありません。" #: ../source/discussions/downstream-packaging.rst:300 msgid "Support downstream testing" -msgstr "" +msgstr "ダウンストリーム側のテストをサポートする" #: ../source/discussions/downstream-packaging.rst:305 msgid "" @@ -1640,27 +1667,40 @@ msgid "" "minimal smoke testing to comprehensive runs of the complete test suite. " "There can be various reasons for doing this, for example:" msgstr "" +"さまざまなダウンストリームプロジェクトが、何らかの形でパッケージ済みの " +"Python プロジェクトのテストを走らせています。これは、それぞれのケースに依っ" +"て、最低限のスモークテストからテストスイートを隅から隅まで網羅的に行うところ" +"までの幅を持ちます。こうしたことを行うにはさまざまな理由があり得ます:" #: ../source/discussions/downstream-packaging.rst:310 msgid "Verifying that the downstream packaging did not introduce any bugs." msgstr "" +"ダウンストリームのパッケージングがどんなバグも持ち込まないようにするために検" +"証すること。" #: ../source/discussions/downstream-packaging.rst:312 msgid "" "Testing on additional platforms that are not covered by upstream testing." msgstr "" +"アップストリームのテストではカバーされていない追加的なプラットフォームでのテ" +"ストを行うこと。" #: ../source/discussions/downstream-packaging.rst:314 msgid "" "Finding subtle bugs that can only be reproduced with particular hardware, " "system package versions, and so on." msgstr "" +"特定のハードウェアやシステムパッケージのバージョンといったものだけで再現し得" +"る些細なバグを探索すること。" #: ../source/discussions/downstream-packaging.rst:317 msgid "" "Testing the released package against newer (or older) dependency versions " "than the ones present during upstream release testing." msgstr "" +"アップストリーム側でのリリース時のテストで使われたものに比べて、より新しい " +"(またはより古い) 依存先バージョンに対してリリース済パッケージをテストするこ" +"と。" #: ../source/discussions/downstream-packaging.rst:320 msgid "" @@ -1669,12 +1709,19 @@ msgid "" "different installed packages, including packages that are not dependencies " "of your package, but nevertheless can cause issues." msgstr "" +"本番構成に非常によく似た環境でパッケージをテストすること。これによって、パッ" +"ケージ自身の依存関係先ではないパッケージを含めて、異なるインストール済パッ" +"ケージとの間の自明でない相互作用によって引き起こされる問題点を検出することが" +"できます。" #: ../source/discussions/downstream-packaging.rst:325 msgid "" "Testing the released package against newer Python versions (including newer " "point releases), or less tested Python implementations such as PyPy." msgstr "" +"リリースされたパッケージを、 (ポイントリリースを含めて) より新しい Python の" +"バージョンや、よりテストされていない PyPy のような Python 実装に対してテスト" +"すること。" #: ../source/discussions/downstream-packaging.rst:328 msgid "" @@ -1686,6 +1733,14 @@ msgid "" "downstream packagers are doing their best to double-check their results, and " "help upstream maintainers triage and fix the bugs that they reported." msgstr "" +"確かに、ダウンストリーム側でテストを行うと、偽陽性や、アップストリーム側プロ" +"ジェクトがサポートする上で興味を持たないようなシナリオについてのバグ報告を生" +"み出すかもしれません。しかしながら、おそらく、もっとよくあるのは、問題に関す" +"る早期の気付きを得たり、発見できなければアップストリーム側プロジェクトのユー" +"ザにとっての問題を引き起こしたであろう非自明のバグを発見したりということで" +"しょう。過誤は起きるものですが、ダウンストリーム側パッケージ作業者の大半は、" +"結果をダブルチェックすることに最善の努力を行っていますし、自分たちが報告した" +"バグをアップストリーム側の保守者が優先順位を付けて修正することを助けます。" #: ../source/discussions/downstream-packaging.rst:339 msgid "" @@ -1696,12 +1751,19 @@ msgid "" "use for everyone, not just downstream packagers. Some specific suggestions " "are:" msgstr "" +"ダウンストリーム側の再パッケージ作業者がそのパッケージを効率よく効果的にテス" +"トするのを助けるために、アップストリーム側プロジェクトができることは、すでに" +"上述した示唆のいくつかを含めて沢山あります。これらは、典型的には、テストス" +"イートが誰にとってもより信頼できて簡単に使えるようにするような改善です。いく" +"つかの特定の示唆は:" #: ../source/discussions/downstream-packaging.rst:345 msgid "" "Include the test files and fixtures in the source distribution, or make it " "possible to easily download them separately." msgstr "" +"テストファイルと必要品はソースコード配布物の中に含めておくか、簡単に個別にダ" +"ウンロードできるようにしておきましょう。" #: ../source/discussions/downstream-packaging.rst:348 msgid "" @@ -1710,6 +1772,10 @@ msgid "" "modifications performed during testing and temporary test files may end up " "being part of the installed package!" msgstr "" +"テストを実行している間は、パッケージのディレクトリに書き込んではいけません。" +"ダウンストリーム側のテスト構成は、インストールパッケージのトップディレクトリ" +"で実行される場合があり、テスト実行中の修正や一時的なテストファイルがインス" +"トールパッケージの一部となってしまうかもしれません！" #: ../source/discussions/downstream-packaging.rst:353 msgid "" @@ -1719,6 +1785,13 @@ msgid "" "Use pytest-socket_ to verify that your tests work offline. This often makes " "your own test workflows faster and more reliable as well." msgstr "" +"テストスイートがオフラインで動作するように作ってください。 responses_ や " +"vcrpy_ のようなパッケージを使って、ネットワークとの相互作用を疑似的に行ってく" +"ださい。もし可能であれば、たとえば pytest_ マーカを経由するなどして、インター" +"ネットアクセスを伴うテストを簡単に無効にできるようにしてください。テストがオ" +"フラインで動作可能であることを検証するには、 pytest-socket_ を使ってくださ" +"い。このようにすることで、テストワークフローがより素早く、かつ、より信頼でき" +"る形で実行できるようになります。" #: ../source/discussions/downstream-packaging.rst:359 msgid "" @@ -1727,6 +1800,10 @@ msgid "" "system services such as databases — in an extreme case, you could crash a " "production service!" msgstr "" +"テストが特別な設定なしで動作するようにするか、または、必要な設定をテストの必" +"要物の一部として行うようにしましょう。データベースのようなシステム側のサービ" +"スに接続することができるとは絶対に仮定しないでください -- とんでもない場合に" +"は、供用中のサービスをクラッシュさせるかもしれませんよ！" #: ../source/discussions/downstream-packaging.rst:364 msgid "" @@ -1734,6 +1811,10 @@ msgid "" "well. Either skip them if the needed packages are not installed, or add " "markers to make deselecting easy." msgstr "" +"パッケージがオプションの依存関係を持つなら、その部分のテストもまたオプション" +"にしましょう。必要なパッケージがインストールされていなければ、そのようなテス" +"トをスキップするか、簡単に選択外にすることができるようなマーカを追加しましょ" +"う。" #: ../source/discussions/downstream-packaging.rst:368 msgid "" @@ -1741,6 +1822,9 @@ msgid "" "include e.g. significant space usage, significant memory usage, long " "runtime, incompatibility with parallel testing." msgstr "" +"もっと一般的に、特別な要求事項を伴うテストにはマーカを付けましょう。これに" +"は、例えば、相当な記憶スペースを使用する、相当なメモリを使用する、長時間を要" +"する、並行でテストを走らせることができない、などが含まれます。" #: ../source/discussions/downstream-packaging.rst:372 msgid "" @@ -1749,6 +1833,11 @@ msgid "" "dependency versions. Assert for warnings using ``pytest.warns()`` rather " "than ``pytest.raises()``!" msgstr "" +"テストスイートが ``-Werror`` 付きで実行されるであろうと仮定してはなりません。" +"それは、例えばより新しい依存関係のバージョンなどのせいで偽陽性を引き起こすの" +"で、往々にしてダウンストリーム側では無効にする必要があります。 ``pytest." +"raises()`` を使うよりも ``pytest.warns()`` を使って警告をアサートしてくださ" +"い！" #: ../source/discussions/downstream-packaging.rst:377 msgid "" @@ -1758,6 +1847,11 @@ msgid "" "its advantages, but you want to have static test cases for completeness as " "well." msgstr "" +"テストスイートが信頼できて再現可能なものになることを目指しましょう。当てにな" +"らないテストを避けましょう。浮動小数点計算や操作のタイミングの結果をそのまま" +"信頼することなど、特別なプラットフォームの細部に依存するものを避けましょう。" +"ファジングには利点もありますが、完全性を期すための静的なテストも持っておきた" +"いでしょう。" #: ../source/discussions/downstream-packaging.rst:383 msgid "" @@ -1769,6 +1863,13 @@ msgid "" "upgraded or the system is under load, without actually affecting the package " "itself." msgstr "" +"その目的に従ってテストを分割し、重要でないカテゴリや問題含みのカテゴリを簡単" +"にスキップできるようにしましょう。ダウンストリーム側でのテストの一義的な目的" +"は、そのパッケージ自体が動作することを保証することであって、一般的に、ダウン" +"ストリーム側ではコードカバー率・コードフォーマット・型チェックやベンチマーク" +"するというようなタスクには興味がありません。パッケージ自体に実際に影響を与え" +"ることはなくとも、依存関係先がアップグレードされたりシステムが高負荷下にあっ" +"たりするとこれらのテストが失敗する可能性があります。" #: ../source/discussions/downstream-packaging.rst:390 msgid "" @@ -1777,6 +1878,10 @@ msgid "" "them all takes a lot of time. Using pytest-xdist_ can help them avoid " "bottlenecks." msgstr "" +"テストスイートの実行に非常に長い時間がかかるなら、並行テストをサポートしま" +"しょう。ダウンストリーム側は、しばしば、多数のパッケージを維持管理していて、" +"それらを全てテストするには長い時間がかかります。ボトルネックを避けるには、 " +"pytest-xdist_ を使うことが助けとなるでしょう。" #: ../source/discussions/downstream-packaging.rst:395 msgid "" @@ -1789,12 +1894,23 @@ msgid "" "``pytest``: ``pytest`` is able to find and execute almost all test cases " "that are compatible with the standard library's ``unittest`` test discovery." msgstr "" +"理想としては、テストスイートを " +"``pytest``を通じて走らせることをサポートしてください。 pytest_ " +"は、テストを便利に非選択にしたり、当てにならないテストを (pytest-" +"rerunfailures_を通じて) 再実行したり、" +"テストがハングアップしてしまうのを防ぐためのタイムアウトを (pytest-timeout_ " +"を通じて) 追加したり、 (pytest-xdist_ を通じて) " +"テストを並行して走らせたり、といったダウンストリーム側に真に役立つ多くのコマ" +"ンドライン引数を持っています。テストスイートが ``pytest`` と一緒に " +"*書かれている* ことや ``pytest`` と一緒に *実行される* " +"必要はないことを覚えておいてください: ``pytest`` は、標準ライブラリの " +"``unittest`` " +"テスト探索と互換性のあるほぼ全てのテストケースを探索して実行することができま" +"す。" #: ../source/discussions/downstream-packaging.rst:409 -#, fuzzy -#| msgid "Final releases" msgid "Aim for stable releases" -msgstr "最終リリース" +msgstr "安定版リリースの目的" #: ../source/discussions/downstream-packaging.rst:414 msgid "" @@ -3519,7 +3635,7 @@ msgstr "" "ます。" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "セマンティックバージョニング" @@ -5159,7 +5275,7 @@ msgstr "説明" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "例" @@ -11054,12 +11170,23 @@ msgstr "" "`cibuildwheel` にある GitHub Action の例を調べてみてください。" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +#, fuzzy +#| msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "信頼された出版 を設定する" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 -msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +#, fuzzy +#| msgid "" +#| "This guide relies on PyPI's `trusted publishing`_ implementation to " +#| "connect to `GitHub Actions CI/CD`_. This is recommended for security " +#| "reasons, since the generated tokens are created for each of your projects " +#| "individually and expire automatically. Otherwise, you'll need to generate " +#| "an `API token`_ for both PyPI and TestPyPI. In case of publishing to " +#| "third-party indexes like :doc:`devpi `, you may need to " +#| "provide a username/password combination." +msgid "" +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -11076,11 +11203,18 @@ msgstr "" "の組み合わせを提供する必要があるかもしれません。" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:35 +#, fuzzy +#| msgid "" +#| "Since this guide will demonstrate uploading to both PyPI and TestPyPI, " +#| "we'll need two trusted publishers configured. The following steps will " +#| "lead you through creating the \"pending\" publishers for your new :term:" +#| "`PyPI project `. However it is also possible to add `trusted " +#| "publishing`_ to any pre-existing project, if you are its owner." msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" "このガイドではPyPIとTestPyPIの両方へのアップロードを実証しますので、ふたつの" @@ -11237,6 +11371,15 @@ msgid "Defining a workflow job environment" msgstr "ワークフローのジョブ環境を定義する" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:130 +#, fuzzy +#| msgid "" +#| "Now, let's add initial setup for our job that will publish to PyPI. It's " +#| "a process that will execute commands that we'll define later. In this " +#| "guide, we'll use the latest stable Ubuntu LTS version provided by GitHub " +#| "Actions. This also defines a GitHub Environment for the job to run in its " +#| "context and a URL to be displayed in GitHub's UI nicely. Additionally, it " +#| "allows acquiring an OpenID Connect token that the ``pypi-publish`` " +#| "actions needs to implement secretless trusted publishing to PyPI." msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -11244,7 +11387,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" "さて、PyPI へ公開 する予定のジョブに初期設定を追加しましょう。それ" "は、後ほど定義するであろうコマンドを実行するプロセスです。このガイド文書で" @@ -11283,70 +11426,19 @@ msgstr "" "Action: を使って、 ``dist/`` フォルダの内容物を無条件に PyPI へアップロードし" "ます。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "配布パッケージに署名する" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" -"以下に述べるジョブは、`CPython ` " -"に署名するのに使われる`_ ものと同じアーティファクトである `Sigstore`_ を使っ" -"て配布パッケージに署名します。" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" -"第一に、配布物パッケージに署名するのに `sigstore/gh-action-sigstore-python " -"GitHub Action`_ を使います。次の段階では、現在のタグから空の GitHub Release " -"が``hg`` CLI を使って作成されます。この段階をさらにカスタマイズすることができ" -"る点に留意してください。リファレンスとしては、`gh リリース説明文書 `_ を見てください。" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" -"GitHub リリースの作成ができるような ``GITHUB_TOKEN`` パーミッションを維持する" -"必要があります。やり方については、 `GitHub 説明文書 `_ を見てくださ" -"い。具体的に言えば、トークンには ``contents: write`` 権限が必要です。" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "最後に、署名された配布物が GitHub Release へアップロードされます。" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -"これは、 `PyPI から削除された `_ GPG 署名を代替するものです。しかしながら、このジョブは PyPI " -"へアップロードする時に必須のものと言うわけではなく、省略することもできます。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "TestPyPI へ公開 するもうひとつのワークフロー" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11354,7 +11446,7 @@ msgstr "" "さて、これらのステップを繰り返して、 ``jobs`` セクションに TestPyPI パッケー" "ジインデックスに公開 するようなもうひとつのジョブを作成しましょう:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11365,22 +11457,22 @@ msgstr "" "いて、使われるとすればリリースの公開 パイプラインが健全であることを" "示すためであることが多いのです。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "CI/CD ワークフローの全体像" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "この段落には、上述のガイド文書に従った場合のワークフローの全体像を披露しま" "す。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "これでできましたよ、皆さん!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11393,7 +11485,7 @@ msgstr "" "にテストビルドを提供するためにも、あなたのリリースパイプラインが健全な状態に" "保たれていることを確認するためにも役に立ちます!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11408,7 +11500,7 @@ msgstr "" "で :ref:`pypiserver` のような PyPI と互換のあるサーバを使うように構成すること" "かもしれません。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -17946,7 +18038,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "歴史" @@ -30145,7 +30237,7 @@ msgstr "" "2022年9月: :pep:`625` を通じて、ソースコード配布物のファイル名を標準化した。" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "バージョン指定子" @@ -30793,7 +30885,18 @@ msgid "" msgstr "" "開発リリースは、また、プレリリースやポストリリースにおいても許されます::" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +#, fuzzy +#| msgid "" +#| "Developmental releases are also permitted for pre-releases and post-" +#| "releases::" +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" +"開発リリースは、また、プレリリースやポストリリースにおいても許されます::" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -30808,7 +30911,7 @@ msgstr "" "奨とされています。そのようなリリースを公開する必要があるなら、数字部分を増加" "させた新しいプレリリースを代わりに作成する方が、よほどわかりやすいでしょう。" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " @@ -30818,11 +30921,11 @@ msgstr "" "変更を含む可能性のあるフルメンテナンスリリースをポストリリースと表記している" "プロジェクトには適切かもしれません。" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "バージョンエポック" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" @@ -30830,13 +30933,13 @@ msgstr "" "バージョン識別子に含まれる場合、エポックは、エクスクラメーションマークでリ" "リース番号構成部分と仕切られて、他のすべての構成部分よりも前に出現します::" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" "明示的にエポックが示されていない場合は、エポックとして ``0`` を暗黙のうちに仮" "定します。" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -30854,7 +30957,7 @@ msgstr "" "ば、通常の順序付けの枠組みを適用した時に、新しいリリースが日付ベースのバー" "ジョン番号よりも *よりふるいもの* として識別されてしまうでしょう::" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " @@ -30864,11 +30967,11 @@ msgstr "" "のバージョン番号が、より古いエポックに属するものよりも後に続くものとして順序" "付けされるので、ソートの順序を適切に変更することができます::" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "正規化" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -30881,11 +30984,11 @@ msgstr "" "なければなりませんが、しかし、そのようなバージョン番号は上述の標準的なシン" "タックスに \"正規化\" されるべきです。" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "ケースセンシティビティ" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " @@ -30895,11 +30998,11 @@ msgstr "" "されるべきであり、標準系は小文字です。これによって、 ``1.1rc1`` に標準化され" "るであろう `1.1RC1`` のようなバージョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "整数の標準化" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -30913,11 +31016,11 @@ msgstr "" "うなローカルバージョンで標準化済みのもののアルファベットと数字から成る構成部" "分の中では、これは適用されません。" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "プレリリースのセパレータ" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -30933,11 +31036,11 @@ msgstr "" "号と数字部分の間に使われるセパレータをも許容するべきです。これによって、 " "``1.0a1`` に標準化される ``1.0a.1`` のようなバージョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "プレリリースの綴り方" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -30953,11 +31056,11 @@ msgstr "" "ジョン番号を許容します。それぞれのケースで、追加的な綴り方の部分は標準的な形" "式のものと同等であると見做されます。" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "明示しないプレリリース番号" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -30969,11 +31072,11 @@ msgstr "" "く形です。これによって、標準化すれば ``1.2a0`` になる ``1.2a`` のようなバー" "ジョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "ポストリリースのセパレータ" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -30991,11 +31094,11 @@ msgstr "" "レータを置くことを許容します。これによって、標準化すれば ``1.2.post2`` となる" "であろう ``1.2.port-2`` のようなバージョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "ポストリリースの綴り方" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -31007,11 +31110,11 @@ msgstr "" "ン番号を許容します。プレリリースでの追加の綴り方と同様に、その標準形式と同等" "のものと見做されるべきです。" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "明示されないポストリリース番号" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -31023,11 +31126,11 @@ msgstr "" "を含めることです。これによって、標準化すれば ``1.2.post0`` となる ``1.2." "post`` のようなバージョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "暗黙裡のポストリリース" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -31043,11 +31146,11 @@ msgstr "" "われてはなりません。換言すれば、 ``1.0-`` は正当なバージョン番号では *なく" "* 、 ``1.0.post0`` へ標準化されることも *ありません* 。" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "開発リリース番号のセパレータ" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -31059,11 +31162,11 @@ msgstr "" "を使う形です。これによって、標準化すれば ``1.2.dev2`` になるであろう ``1.2-" "dev2`` や ``1.2dev2`` のようなバージョン番号を許容します。" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "暗黙裡の開発バージョン番号" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -31075,11 +31178,11 @@ msgstr "" "れによって、標準化すれば ``1.2.dev0`` となる ``1.2.dev`` のようなバージョン番" "号を許容します。" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "ローカルのバージョン番号構成部分" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -31091,11 +31194,11 @@ msgstr "" "ことです。これによって、標準化すれば ``1.0+ubuntu.1`` となる " "``1.0+ubuntu-1`` のようなバージョン番号も許容されます。" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "先駆する v の文字" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -31109,11 +31212,11 @@ msgstr "" "は省略されるべきです。 ``v`` の有無だけが異なるバージョン番号は、同一のものと" "見做されます。" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "先行する空白文字や後続する空白文字" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -31127,11 +31230,11 @@ msgstr "" "す。これによって、標準化すれば ``1.0`` となる ``1.0\\n`` のようなバージョン番" "号に見られる、偶然に入り込んだ空白文字を実用的に取り扱うことができます。" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "枠組みに合致したバージョン番号の例" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -31147,7 +31250,7 @@ msgstr "" "ユーザにとってはバージョン番号間の相対的な順序を解き明かすことに困難を感じる" "ことになるでしょう。" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -31158,22 +31261,22 @@ msgstr "" "るアプローチで、 \"最新リリース\" と \"最新のステーブルリリース\" を人間も自" "動化ツールも簡単に決定できることが保証されたもののいくつかの例を示します。" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "単純な \"メジャー.マイナー\" バージョン付け::" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "単純な \"メジャー.マイナー.マイクロ\" バージョン付け::" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" "アルファ・ベータや公開候補 のようなプレリリースを伴う \"メジャー." "マイナー\" バージョン付け::" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" @@ -31181,18 +31284,18 @@ msgstr "" "開発リリース 、リリース候補 や" "ポストリリースのある \"メジャー.マイナー\" バージョン付け::" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" "ゼロを飛ばして各年の中で増加するシリアル値を使った日付ベースのリリース番号::" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "許容される接尾辞と相対的な順序付けのまとめ" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " @@ -31202,7 +31305,7 @@ msgstr "" "というよりは、むしろ、一義的には配布物のメタデータを自動的に処理するツールの" "作者に向けて書かれています。" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " @@ -31212,7 +31315,7 @@ msgstr "" "序されなければなりません。エポック構成部分が存在しない場合には、暗黙のうちに " "``0`` の値と解釈します。" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " @@ -31222,7 +31325,7 @@ msgstr "" "時には以下のように Python のタプルソーティングと同じ順序で格納されていなけれ" "ばなりません::" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." @@ -31230,7 +31333,7 @@ msgstr "" "比較に関わるすべてのリリース構成部分は、必要に応じて不足する構成部分にゼロを" "補填することで長さを一致させなければなりません。" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" @@ -31238,7 +31341,7 @@ msgstr "" "リリース番号の数字部分 (``1.0`` や ``2.7.3``) の中では、後述の接尾辞が許され" "ており、下に示す通りに順序付けをしなければなりません::" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -31251,7 +31354,7 @@ msgstr "" "合には曖昧であるとしてこれを拒否しても構いませんが、これでも仕様には合致して" "います。" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " @@ -31261,7 +31364,7 @@ msgstr "" "(``1.0rc1``, ``1.0c1``) の中では、後述の接尾辞が許されていて、示される通りに" "並べ替えられなければなりません::" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" @@ -31269,7 +31372,7 @@ msgstr "" "ポストリリース (``1.0.post1``) の中では、後述の接尾辞が許されていて、示す通り" "に並べ替えられなければなりません::" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." @@ -31279,7 +31382,7 @@ msgstr "" "post1``) であっても、 ``devN`` と ``postN`` は、常にドットに後続しなければな" "らないことを銘記してください。" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." @@ -31288,15 +31391,15 @@ msgstr "" "発リリース構成部分の中で、数値部分の値に従って順序付けをしなければなりませ" "ん。" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "可能なバージョン番号の例を以下に示します::" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "相異なるメタデータバージョンを通してバージョン番号を順序付けする" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" @@ -31306,7 +31409,7 @@ msgstr "" "ジョン番号の識別や順序付けの枠組みを指定していません。しかしながら、メタデー" "タ v1.2 (:pep:`345`) では、 :pep:`386` で定義された枠組みを指定しています。" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -31324,7 +31427,7 @@ msgstr "" "よって、あるプロジェクトのすべてのバージョンにおいてひとつの解析メカニズムが" "使われるような標準化が必要とされます。" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -31340,7 +31443,7 @@ msgstr "" "つも利用可能でない時には、それぞれの実装で定義されたバージョン番号の解釈や順" "序付けにフォールバックしても構いません。" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." @@ -31348,11 +31451,11 @@ msgstr "" "配布物のユーザは、自分が管理するプライベートなパッケージインデックスにおい" "て、合致しないバージョン番号を明示的に除去しても構いません。" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "他のバージョン番号の枠組みとの互換性" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -31366,7 +31469,7 @@ msgstr "" "タに格納しておく一方で、公開のバージョン番号を version フィールドに置くことが" "できます。" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " @@ -31377,7 +31480,7 @@ msgstr "" "のプロジェクト向けに好みの内部的なバージョン番号枠組みを使うことが許されま" "す。" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -31394,7 +31497,7 @@ msgstr "" "る配布物を公開する時に発生する多くの課題を網羅するためにも、この枠組みは理解" "しておくに値します。" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -31406,7 +31509,7 @@ msgstr "" "この仕様で定義されるバージョン番号枠組みと完全に互換であり、この形を受容する" "ことが推奨されています。" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " @@ -31416,7 +31519,7 @@ msgstr "" "号を含むセマンティックバージョン (builds - clause 11) は、この仕様と *互換性" "がなく* 、公開のバージョン番号フィールドでは許されていません。" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " @@ -31426,17 +31529,17 @@ msgstr "" "番号と互換性のあるものに翻訳する可能なメカニズムの一つは、 ``.devN`` 接尾辞を" "使って適切なバージョン番号の順序を指定することです。" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" "特定のビルド情報も、ローカルのバージョン番号のラベルに含めても構いません。" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "DVCS に基づいたバージョン番号のラベル" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -31448,7 +31551,7 @@ msgstr "" "ハッシュ値は信頼できる形で順序付けすることができないので、そのようなバージョ" "ン番号は公開のバージョンフィールドでは許されません。" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " @@ -31458,18 +31561,18 @@ msgstr "" "ジェクトのメタデータに格納することができない一方で、そのようなリリースを公開" "する際に一意に識別するために、公開の ``.devN`` 接尾辞をつけても構いません。" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" "ハッシュ値の情報を識別することは、ローカルのバージョン番号ラベルに含めても構" "いません。" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "Olson データベースによるバージョニング" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " @@ -31479,7 +31582,7 @@ msgstr "" "タベースのバージョニング方法から継承しています: 年と、それに後続する小文字の" "文字でその年の中でのデータベースのバージョンを示すもの。" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -31491,7 +31594,7 @@ msgstr "" "０か１から始まって、その年の内にデータベースが更新される度に１づつ増加されま" "す。" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." @@ -31499,7 +31602,7 @@ msgstr "" "他の翻訳されたバージョン識別子と同様に、対応する Olson データベースのバージョ" "ン番号は、そのプロジェクトのメタデータに記録しておくことが可能です。" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" @@ -31507,37 +31610,37 @@ msgstr "" "バージョン指定子は、一連のバージョン番号節をコンマで区切ったものから構成され" "ます。例えば::" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "比較演算子がバージョン番号節の種類を決定します:" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: `互換性のあるリリース `_ 節" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "``==``: `バージョン番号のマッチング `_ 節" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: `バージョンの除外 `_ 節" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" "``<=``, ``>=``: `境界を含む順序比較 `_ 節" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" "``<``, ``>``: `境界を含まない順序比較 `_ 節" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: `あらゆる意味での同一性 `_ clause." -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " @@ -31547,7 +31650,7 @@ msgstr "" "全体として指定子に合致するために、すべての与えられた節が合致しなければなりま" "せん。" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." @@ -31555,7 +31658,7 @@ msgstr "" "条件演算子とその後のバージョン識別子の間の空白文字は、コンマの周囲の空白文字" "と同様にオプションです。" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -31569,7 +31672,7 @@ msgstr "" "だと見做されるか否かは、 `プレリリースの取り扱い `_ に記述されているとおりに扱われるべきです。" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " @@ -31579,11 +31682,11 @@ msgstr "" "定子は許されてはならず、あるバージョン指定子に合致する候補バージョンかどうか" "を調べる際にはローカルバージョンラベルは完全に無視されなければなりません。" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "互換性のあるリリース " -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " @@ -31593,7 +31696,7 @@ msgstr "" "成されます。指定されたバージョンと互換性があるものと期待されるすべての候補" "バージョンに合致します。" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " @@ -31603,7 +31706,7 @@ msgstr "" "された標準フォーマットの範疇に収まっていなければなりません。ローカルバージョ" "ン識別子は、このバージョン識別子の中では許容されません。" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" @@ -31611,7 +31714,7 @@ msgstr "" "あるリリース識別子 ``V.N`` にとって、互換リリース節は、一組の比較節とほぼ同一" "のものです::" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." @@ -31619,11 +31722,11 @@ msgstr "" "この演算子は、 ``~=1`` のように単独の構成部分バージョン番号と一緒に用いてはな" "りません。" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "例えば、次に挙げるバージョン番号群はすべて同等ということになります::" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " @@ -31633,7 +31736,7 @@ msgstr "" "換性のあるリリース節の形の名前を付けられているなら、要求される接頭辞と合致す" "るかどうかを決める時には接尾辞が無視されます::" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " @@ -31643,11 +31746,11 @@ msgstr "" "節での前方互換性に想定された度合いを、バージョン識別子の後ろにゼロを追加して" "制御することが可能です::" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "バージョン番号の照合" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." @@ -31655,7 +31758,7 @@ msgstr "" "バージョン番号マッチング節には、バージョン番号マッチング演算子 ``==`` とバー" "ジョン識別子を含みます。" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " @@ -31665,7 +31768,7 @@ msgstr "" "マットでなければなりませんが、公開のバージョン識別子における後続する ``.*`` " "は以下に述べるように許されています。" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -31678,7 +31781,7 @@ msgstr "" "*唯一の* 置換が行われるのは、リリース番号構成部分を同じ長さで行うことを保証す" "るために、リリース番号構成部分にゼロをパディングする時だけです。" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -31689,7 +31792,7 @@ msgstr "" "スによって変わります。自動化されたツール群は、厳密なバージョンマッチングが使" "用された時には、少なくとも警告を発するべきで、全てを拒絶しても構いません。" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -31705,8 +31808,8 @@ msgstr "" "分だけを含んでいるなら、リリース番号構成部分の中の後続の構成部分 (あるいは、" "その欠落) もまた、無視されます。" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" @@ -31714,7 +31817,7 @@ msgstr "" "例えば、あるバージョン番号 ``1.1.post1`` が与えられたとして、以下に示すように" "合致したり合致しなかったりします::" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " @@ -31724,7 +31827,7 @@ msgstr "" "``.`` を持つものと見なされ、従って、バージョン番号 ``1.1a1`` が与えられたとす" "れば、以下に示すように合致したり合致しなかったりします::" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -31736,7 +31839,7 @@ msgstr "" "れます。バージョン番号 ``1.1`` が与えられたなら、以下に示すように合致したり合" "致しなかったりします::" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -31750,7 +31853,7 @@ msgstr "" "番号は比較の目的においては無視されるので、そのようなものが接頭辞マッチにあっ" "たとしても意味を成しません。" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -31765,7 +31868,7 @@ msgstr "" "義的に、共有の配布物インデックスを使う上で繰り返し可能な *アプリケーションの" "展開* のための依存関係を定義するために使われることを想定しています。" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " @@ -31775,7 +31878,7 @@ msgstr "" "ジョン識別子であり、候補バージョンに付けられたローカルバージョン番号ラベル" "は、バージョンマッチングの際には無視されなければなりません。" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -31788,11 +31891,11 @@ msgstr "" "バージョン識別子と合致するか確かめられ、ローカルバージョンラベルは厳密な文字" "列の同一性比較を使って同一であるかどうか確認されます。" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "バージョンの除外 " -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." @@ -31800,7 +31903,7 @@ msgstr "" "バージョンの除外節は、バージョン除外演算子 ``!=`` とバージョン識別子を含みま" "す。" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " @@ -31810,11 +31913,11 @@ msgstr "" "る点を除けば `バージョン番号のマッチング `_ 演算子のそれと" "同一です。" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "境界を含む順序比較 " -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -31827,12 +31930,12 @@ msgstr "" "み `_ によって定義される首尾一貫した順序付けに基づいてその比" "較が正しいかどうかを任意のバージョン番号に対して行います。" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "境界を含む順序比較の演算子は ``<=`` と ``>=`` です。" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." @@ -31841,16 +31944,16 @@ msgstr "" "ることを担保するために、リリース番号構成部分は必要に応じてゼロでパディングさ" "れます。" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "ローカルバージョン識別子は、このバージョン識別子の中では許されません。" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "境界を含まない順序比較 " -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -31865,7 +31968,7 @@ msgstr "" "と似ています。しかしながら、指定されたバージョン番号のプレリリース・ポストリ" "リース・ローカルバージョンの部分を除外します。" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -31881,7 +31984,7 @@ msgstr "" "ますが ``1.7.0.post1`` を許容せず、 ``>1.7.post2`` は ``1.7.1`` や ``1.7.0." "post3`` を許容しますが ``1.7.0`` を許容しません。" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." @@ -31889,7 +31992,7 @@ msgstr "" "境界を含まない順序比較 ``>V`` は、指定されたバージョン番号のローカルバージョ" "ン部分と **比較してはなりません**。" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``" -#: ../source/specifications/version-specifiers.rst:1014 +#: ../source/specifications/version-specifiers.rst:1017 msgid "" "Arbitrary equality comparisons are simple string equality operations which " "do not take into account any of the semantic information such as zero " @@ -31917,7 +32020,7 @@ msgstr "" "``==`` 演算子なら実行するようなプレフィクスのマッチングもサポートしていませ" "ん。" -#: ../source/specifications/version-specifiers.rst:1019 +#: ../source/specifications/version-specifiers.rst:1022 msgid "" "The primary use case for arbitrary equality is to allow for specifying a " "version which cannot otherwise be represented by this specification. This " @@ -31931,14 +32034,14 @@ msgstr "" "ればこの仕様とは非互換になってしまうようなレガシーなバージョンを、それでもイ" "ンストールすることができる脱出ハッチとして振舞います。" -#: ../source/specifications/version-specifiers.rst:1025 +#: ../source/specifications/version-specifiers.rst:1028 msgid "" "An example would be ``===foobar`` which would match a version of ``foobar``." msgstr "" "一つの例としては、``foobar`` というバージョン番号に合致するであろう " "``==foobar`` ということになるでしょう。" -#: ../source/specifications/version-specifiers.rst:1027 +#: ../source/specifications/version-specifiers.rst:1030 msgid "" "This operator may also be used to explicitly require an unpatched version of " "a project such as ``===1.0`` which would not match for a version " @@ -31948,7 +32051,7 @@ msgstr "" "うと思われる、 ``===1.0`` のようなプロジェクトのパッチ適用のないバージョンを" "明示的に要求するためにも使われます。" -#: ../source/specifications/version-specifiers.rst:1031 +#: ../source/specifications/version-specifiers.rst:1034 msgid "" "Use of this operator is heavily discouraged and tooling MAY display a " "warning when it is used." @@ -31956,11 +32059,11 @@ msgstr "" "この演算子の使用は強い非推奨の状態にあり、使用に際してはツール類は警告を表示" "しても構いません。" -#: ../source/specifications/version-specifiers.rst:1036 +#: ../source/specifications/version-specifiers.rst:1039 msgid "Handling of pre-releases" msgstr "プレリリースの取り扱い " -#: ../source/specifications/version-specifiers.rst:1038 +#: ../source/specifications/version-specifiers.rst:1041 msgid "" "Pre-releases of any kind, including developmental releases, are implicitly " "excluded from all version specifiers, *unless* they are already present on " @@ -31972,18 +32075,18 @@ msgstr "" "か、の *いずれかでない限り* 、開発リリースを含むプレリリースは、どんな種類で" "も、あらゆるバージョン指定子から暗黙裡に除外されます。" -#: ../source/specifications/version-specifiers.rst:1043 +#: ../source/specifications/version-specifiers.rst:1046 msgid "By default, dependency resolution tools SHOULD:" msgstr "" "デフォルトでは、依存関係を解決しようとするツール類は以下のことを行うべきです:" -#: ../source/specifications/version-specifiers.rst:1045 +#: ../source/specifications/version-specifiers.rst:1048 msgid "accept already installed pre-releases for all version specifiers" msgstr "" "全てのバージョン指定子向けにすでにインストールされているプレリリースを受け入" "れる" -#: ../source/specifications/version-specifiers.rst:1046 +#: ../source/specifications/version-specifiers.rst:1049 msgid "" "accept remotely available pre-releases for version specifiers where there is " "no final or post release that satisfies the version specifier" @@ -31992,11 +32095,11 @@ msgstr "" "モートサイトにあって利用可能なプレリリースを、バージョン指定子として受け入れ" "る" -#: ../source/specifications/version-specifiers.rst:1048 +#: ../source/specifications/version-specifiers.rst:1051 msgid "exclude all other pre-releases from consideration" msgstr "他のすべてのプレリリースを考慮の対象から除外する" -#: ../source/specifications/version-specifiers.rst:1050 +#: ../source/specifications/version-specifiers.rst:1053 msgid "" "Dependency resolution tools MAY issue a warning if a pre-release is needed " "to satisfy a version specifier." @@ -32004,7 +32107,7 @@ msgstr "" "依存関係解決ツール群は、バージョン指定子を満足させるためにあるプレリリースが" "必要である場合には、警告を発しても構いません。" -#: ../source/specifications/version-specifiers.rst:1053 +#: ../source/specifications/version-specifiers.rst:1056 msgid "" "Dependency resolution tools SHOULD also allow users to request the following " "alternative behaviours:" @@ -32012,11 +32115,11 @@ msgstr "" "依存関係解決ツール群は、また、以下のような代替的な振る舞いをユーザが要求する" "ことを許容するべきです:" -#: ../source/specifications/version-specifiers.rst:1056 +#: ../source/specifications/version-specifiers.rst:1059 msgid "accepting pre-releases for all version specifiers" msgstr "全てのバージョン指定子にプレリリースを受け入れること" -#: ../source/specifications/version-specifiers.rst:1057 +#: ../source/specifications/version-specifiers.rst:1060 msgid "" "excluding pre-releases for all version specifiers (reporting an error or " "warning if a pre-release is already installed locally, or if a pre-release " @@ -32026,7 +32129,7 @@ msgstr "" "ローカルにインストールされている場合や特定の指定子を満たすためにはプレリリー" "スが唯一の選択肢である場合には、エラーないし警告を報告すること)" -#: ../source/specifications/version-specifiers.rst:1061 +#: ../source/specifications/version-specifiers.rst:1064 msgid "" "Dependency resolution tools MAY also allow the above behaviour to be " "controlled on a per-distribution basis." @@ -32034,7 +32137,7 @@ msgstr "" "依存関係解決ツール群は、配布物の単位ごとに上記の振る舞いを許容しても構いませ" "ん。" -#: ../source/specifications/version-specifiers.rst:1064 +#: ../source/specifications/version-specifiers.rst:1067 msgid "" "Post-releases and final releases receive no special treatment in version " "specifiers - they are always included unless explicitly excluded." @@ -32042,25 +32145,25 @@ msgstr "" "ポストリリースと最終リリースは、バージョン識別子の中で何ら特別な取り扱いを受" "けません - 明示的に除外されていない限り、これらは常に受け入れられます。" -#: ../source/specifications/version-specifiers.rst:1071 +#: ../source/specifications/version-specifiers.rst:1074 msgid "``~=3.1``: version 3.1 or later, but not version 4.0 or later." msgstr "" "``~=3.1``: バージョン 3.1 またはそれ以降、しかし、バージョン 4.0 またはそれ以" "降ではない。" -#: ../source/specifications/version-specifiers.rst:1072 +#: ../source/specifications/version-specifiers.rst:1075 msgid "``~=3.1.2``: version 3.1.2 or later, but not version 3.2.0 or later." msgstr "" "``~=3.1.2``: バージョン 3.1.2 またはそれ以降、しかし、バージョン 3.2.0 または" "それ以降ではない。" -#: ../source/specifications/version-specifiers.rst:1073 +#: ../source/specifications/version-specifiers.rst:1076 msgid "``~=3.1a1``: version 3.1a1 or later, but not version 4.0 or later." msgstr "" "``~=3.1a1``: バージョン 3.1a1 またはそれ以降、しかし、バージョン 4.0 またはそ" "れ以降ではない。" -#: ../source/specifications/version-specifiers.rst:1074 +#: ../source/specifications/version-specifiers.rst:1077 msgid "" "``== 3.1``: specifically version 3.1 (or 3.1.0), excludes all pre-releases, " "post releases, developmental releases and any 3.1.x maintenance releases." @@ -32068,7 +32171,7 @@ msgstr "" "``== 3.1``: 正確にバージョン 3.1 (または 3.1.0)、プレリリース・ポストリリー" "ス・開発リリースや 3.1.x のメンテナンスリリースは全て除外する。" -#: ../source/specifications/version-specifiers.rst:1076 +#: ../source/specifications/version-specifiers.rst:1079 msgid "" "``== 3.1.*``: any version that starts with 3.1. Equivalent to the " "``~=3.1.0`` compatible release clause." @@ -32076,7 +32179,7 @@ msgstr "" "``== 3.1.*``: 3.1 で始まるすべてのバージョン。 ``~=3.1.0`` 互換リリース節に同" "じ。" -#: ../source/specifications/version-specifiers.rst:1078 +#: ../source/specifications/version-specifiers.rst:1081 msgid "" "``~=3.1.0, != 3.1.3``: version 3.1.0 or later, but not version 3.1.3 and not " "version 3.2.0 or later." @@ -32084,11 +32187,11 @@ msgstr "" "``~=3.1.0, != 3.1.3``: バージョン 3.1.0 またはそれ以降、しかし、バージョン " "3.1.3 ではなく、バージョン 3.2.0 またはそれ以降でもない。" -#: ../source/specifications/version-specifiers.rst:1083 +#: ../source/specifications/version-specifiers.rst:1086 msgid "Direct references" msgstr "直接参照" -#: ../source/specifications/version-specifiers.rst:1085 +#: ../source/specifications/version-specifiers.rst:1088 msgid "" "Some automated tools may permit the use of a direct reference as an " "alternative to a normal version specifier. A direct reference consists of " @@ -32098,7 +32201,7 @@ msgstr "" "ものがあります。直接参照は、それを指定する ``@`` と明示された URL から構成さ" "れます。" -#: ../source/specifications/version-specifiers.rst:1089 +#: ../source/specifications/version-specifiers.rst:1092 msgid "" "Whether or not direct references are appropriate depends on the specific use " "case for the version specifier. Automated tools SHOULD at least issue " @@ -32109,7 +32212,7 @@ msgstr "" "存します。自動化ツール群は、少なくとも警告を発行するべきで、直接参照が不適切" "に使われた場合には全体を拒否しても構いません。" -#: ../source/specifications/version-specifiers.rst:1094 +#: ../source/specifications/version-specifiers.rst:1097 msgid "" "Public index servers SHOULD NOT allow the use of direct references in " "uploaded distributions. Direct references are intended as a tool for " @@ -32119,7 +32222,7 @@ msgstr "" "すべきではありません。直接参照は、公開者 向けではなくてソフト" "ウェアインテグレータ向けのツールとして意図されたものです。" -#: ../source/specifications/version-specifiers.rst:1098 +#: ../source/specifications/version-specifiers.rst:1101 msgid "" "Depending on the use case, some appropriate targets for a direct URL " "reference may be an sdist or a wheel binary archive. The exact URLs and " @@ -32129,16 +32232,16 @@ msgstr "" "バイナリアーカイブでしょう。正確な URL やターゲットのサポートがあるかどうかは" "ツール次第です。" -#: ../source/specifications/version-specifiers.rst:1102 +#: ../source/specifications/version-specifiers.rst:1105 msgid "For example, a local source archive may be referenced directly::" msgstr "" "例えば、ローカルのソースコードアーカイブが直接に参照されるかもしれません::" -#: ../source/specifications/version-specifiers.rst:1106 +#: ../source/specifications/version-specifiers.rst:1109 msgid "Alternatively, a prebuilt archive may also be referenced::" msgstr "あるいは、ビルド済みのアーカイブが参照されるかもしれません::" -#: ../source/specifications/version-specifiers.rst:1110 +#: ../source/specifications/version-specifiers.rst:1113 msgid "" "All direct references that do not refer to a local file URL SHOULD specify a " "secure transport mechanism (such as ``https``) AND include an expected hash " @@ -32158,7 +32261,7 @@ msgstr "" "することを拒否しても構いません。もしそのような直接参照が安全でない転送手段を" "使っているなら、自動化ツールはその URL に依存するべきではありません。" -#: ../source/specifications/version-specifiers.rst:1119 +#: ../source/specifications/version-specifiers.rst:1122 msgid "" "It is RECOMMENDED that only hashes which are unconditionally provided by the " "latest version of the standard library's :py:mod:`hashlib` module be used " @@ -32171,7 +32274,7 @@ msgstr "" "します。本文書の執筆時点では、 'md5' ・ 'sha1' ・ 'sha224' ・ 'sha256' ・ " "'sha384' ・ 'sha512' が該当します。" -#: ../source/specifications/version-specifiers.rst:1125 +#: ../source/specifications/version-specifiers.rst:1128 msgid "" "For source archive and wheel references, an expected hash value may be " "specified by including a ``=`` entry as part " @@ -32181,7 +32284,7 @@ msgstr "" "URL の一部として ``=`` エントリに含まれる形で" "指定されるでしょう。" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -32195,7 +32298,7 @@ msgstr "" "す。自動化ツール群は、ハッシュ値で表したコミット識別子を持たないバージョン管" "理システムではハッシュ値がなくても警告を省略しても構いません。" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -32207,7 +32310,7 @@ msgstr "" "タグ>#<コミットのハッシュ値>`` という表記方法を用いて URL の末尾に追加しても" "構いません。" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -32225,15 +32328,15 @@ msgstr "" "シュ値が含まれているべきであるという要求に従うために、コミットのハッシュ値が" "含まれています。" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "リモート URL の例::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "ファイルを指す URL 群" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -32245,7 +32348,7 @@ msgstr "" "であってさえも３個目のスラッシュが存在していなければなりません。 ```` " "は、これからアクセスされるであろうファイルシステム上のファイルパスです。" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -32257,7 +32360,7 @@ msgstr "" "の FQDN です。換言すれば、 \\*nix 上では、ローカルマシン上のパスにアクセスす" "るための ``file://`` スキームだけが使用可能であるということです。" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -32278,18 +32381,18 @@ msgstr "" "org/web/20130321051043/http://blogs.msdn.com/b/ie/archive/2006/12/06/file-" "uris-in-windows.aspx>`_ を見てください。" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "pkg_resources.parse_version からの相違点のまとめ" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " @@ -32300,7 +32403,7 @@ msgstr "" "いますが、他方で、 ``pkg_resources.parse_version`` はそれ (訳註、ローカルバー" "ジョン) をプレリリースのマーカーの一つであると見做しています。" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " @@ -32310,7 +32413,7 @@ msgstr "" "他方で ``pkg_resources.parse_version`` では *あらゆる* 任意の文字列から何らか" "の意味を汲み取るように試みます。" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " @@ -32321,11 +32424,11 @@ msgstr "" "は、それぞれのタイプが高々一度だけ使われることと、ある順番に従って存在してい" "ることを許容しているだけです。" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "補遺: 正規表現を伴うバージョン文字列を解析する" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -32339,7 +32442,7 @@ msgstr "" "し否であればその後の標準化のためにさまざまな構成要素を引き出すために使うこと" "ができる、そのような正規表現を提供します。" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" @@ -32347,7 +32450,7 @@ msgstr "" "バージョン識別子が正統な書式であるか否かを確かめるためには、次の関数を使うこ" "とができます:" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ プロジェクトによって定" "義されたもの):" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "2014年8月: :pep:`440` を通じてこの仕様が承認された。" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "Python 仮想環境" @@ -34621,6 +34730,63 @@ msgstr "" "りなのであれば、 *通常のパッケージ* と (空のファイルだとしても) ``__init__." "py`` から離れないことをお薦めします。" +#~ msgid "Signing the distribution packages" +#~ msgstr "配布パッケージに署名する" + +#~ msgid "" +#~ "The following job signs the distribution packages with `Sigstore`_, the " +#~ "same artifact signing system `used to sign CPython `_." +#~ msgstr "" +#~ "以下に述べるジョブは、`CPython ` に署名するのに使われる`_ ものと同じアーティファクトである `Sigstore`_ " +#~ "を使って配布パッケージに署名します。" + +#~ msgid "" +#~ "Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ " +#~ "to sign the distribution packages. In the next step, an empty GitHub " +#~ "Release from the current tag is created using the ``gh`` CLI. Note this " +#~ "step can be further customised. See the `gh release documentation " +#~ "`_ as a reference." +#~ msgstr "" +#~ "第一に、配布物パッケージに署名するのに `sigstore/gh-action-sigstore-" +#~ "python GitHub Action`_ を使います。次の段階では、現在のタグから空の " +#~ "GitHub Release が``hg`` CLI を使って作成されます。この段階をさらにカスタマ" +#~ "イズすることができる点に留意してください。リファレンスとしては、`gh リリー" +#~ "ス説明文書 `_ を見てください。" + +#~ msgid "" +#~ "You may need to manage your ``GITHUB_TOKEN`` permissions to enable " +#~ "creating the GitHub Release. See the `GitHub documentation `_ for " +#~ "instructions. Specifically, the token needs the ``contents: write`` " +#~ "permission." +#~ msgstr "" +#~ "GitHub リリースの作成ができるような ``GITHUB_TOKEN`` パーミッションを維持" +#~ "する必要があります。やり方については、 `GitHub 説明文書 `_ を見" +#~ "てください。具体的に言えば、トークンには ``contents: write`` 権限が必要で" +#~ "す。" + +#~ msgid "" +#~ "Finally, the signed distributions are uploaded to the GitHub Release." +#~ msgstr "最後に、署名された配布物が GitHub Release へアップロードされます。" + +#~ msgid "" +#~ "This is a replacement for GPG signatures, for which support has been " +#~ "`removed from PyPI `_. However, this job is not mandatory for uploading to PyPI and can be " +#~ "omitted." +#~ msgstr "" +#~ "これは、 `PyPI から削除された `_ GPG 署名を代替するものです。しかしながら、このジョブは " +#~ "PyPI へアップロードする時に必須のものと言うわけではなく、省略することもで" +#~ "きます。" + #, fuzzy #~| msgid "" #~| "This can take two forms. You can put your license in a file, typically " diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index c5ca85a42..3d2349b0c 100644 --- a/locales/ko/LC_MESSAGES/messages.po +++ b/locales/ko/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-11-03 06:00+0000\n" "Last-Translator: 황인아 \n" "Language-Team: Korean `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8647,7 +8647,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8672,79 +8672,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8752,7 +8718,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8761,7 +8727,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13671,7 +13637,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23159,7 +23125,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23633,7 +23599,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23643,29 +23615,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23676,19 +23648,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23696,23 +23668,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23721,11 +23693,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23735,11 +23707,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23749,11 +23721,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23761,11 +23733,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23776,11 +23748,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23788,11 +23760,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23800,11 +23772,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23814,11 +23786,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23826,11 +23798,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23838,11 +23810,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23850,11 +23822,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23863,11 +23835,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23876,11 +23848,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23890,7 +23862,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23898,69 +23870,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23968,48 +23940,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24020,7 +23992,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24030,17 +24002,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24049,14 +24021,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24067,7 +24039,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24075,30 +24047,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24106,30 +24078,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24137,60 +24109,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24199,79 +24171,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24280,7 +24252,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24288,7 +24260,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24298,21 +24270,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24320,7 +24292,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24329,7 +24301,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24339,14 +24311,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24355,29 +24327,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24386,27 +24358,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24416,7 +24388,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24426,13 +24398,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24652,7 +24624,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24660,7 +24632,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24671,15 +24643,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24687,7 +24659,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24695,7 +24667,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24707,43 +24679,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24752,23 +24724,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/lzh/LC_MESSAGES/messages.po b/locales/lzh/LC_MESSAGES/messages.po index 4e003b3d3..f9d458062 100644 --- a/locales/lzh/LC_MESSAGES/messages.po +++ b/locales/lzh/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-01-31 06:01+0000\n" "Last-Translator: maker \n" "Language-Team: Chinese (Literary) `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8561,7 +8561,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8586,79 +8586,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8666,7 +8632,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8675,7 +8641,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13577,7 +13543,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23030,7 +22996,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23502,7 +23468,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23512,28 +23484,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23544,18 +23516,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23563,22 +23535,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23587,11 +23559,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23601,11 +23573,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23615,11 +23587,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23627,11 +23599,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23642,11 +23614,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23654,11 +23626,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23666,11 +23638,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23680,11 +23652,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23692,11 +23664,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23704,11 +23676,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23716,11 +23688,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23729,11 +23701,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23742,11 +23714,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23756,7 +23728,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23764,69 +23736,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23834,48 +23806,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23886,7 +23858,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23896,17 +23868,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23915,14 +23887,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23933,7 +23905,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23941,30 +23913,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23972,30 +23944,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24003,60 +23975,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24065,79 +24037,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24146,7 +24118,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24154,7 +24126,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24164,21 +24136,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24186,7 +24158,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24195,7 +24167,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24205,14 +24177,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24221,28 +24193,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24251,27 +24223,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24281,7 +24253,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24291,13 +24263,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24517,7 +24489,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24525,7 +24497,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24536,15 +24508,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24552,7 +24524,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24560,7 +24532,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24572,43 +24544,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24617,23 +24589,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/mk/LC_MESSAGES/messages.po b/locales/mk/LC_MESSAGES/messages.po index a75eb2457..914bd45b3 100644 --- a/locales/mk/LC_MESSAGES/messages.po +++ b/locales/mk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2023-10-21 04:04+0000\n" "Last-Translator: \"Kristijan \\\"Fremen\\\" Velkovski\" \n" "Language-Team: Macedonian `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8565,7 +8565,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8590,79 +8590,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8670,7 +8636,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8679,7 +8645,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13583,7 +13549,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23034,7 +23000,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23506,7 +23472,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23516,28 +23488,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23548,18 +23520,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23567,22 +23539,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23591,11 +23563,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23605,11 +23577,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23619,11 +23591,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23631,11 +23603,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23646,11 +23618,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23658,11 +23630,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23670,11 +23642,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23684,11 +23656,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23696,11 +23668,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23708,11 +23680,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23720,11 +23692,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23733,11 +23705,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23746,11 +23718,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23760,7 +23732,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23768,69 +23740,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23838,48 +23810,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23890,7 +23862,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23900,17 +23872,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23919,14 +23891,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23937,7 +23909,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23945,30 +23917,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23976,30 +23948,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24007,60 +23979,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24069,79 +24041,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24150,7 +24122,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24158,7 +24130,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24168,21 +24140,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24190,7 +24162,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24199,7 +24171,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24209,14 +24181,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24225,28 +24197,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24255,27 +24227,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24285,7 +24257,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24295,13 +24267,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24521,7 +24493,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24529,7 +24501,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24540,15 +24512,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24556,7 +24528,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24564,7 +24536,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24576,43 +24548,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24621,23 +24593,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/mr/LC_MESSAGES/messages.po b/locales/mr/LC_MESSAGES/messages.po index fd81fffee..97529c33f 100644 --- a/locales/mr/LC_MESSAGES/messages.po +++ b/locales/mr/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-01-25 14:18+0000\n" "Last-Translator: Prachi Joshi \n" "Language-Team: Marathi `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8558,7 +8558,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8583,79 +8583,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8663,7 +8629,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8672,7 +8638,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13574,7 +13540,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23025,7 +22991,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23497,7 +23463,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23507,28 +23479,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23539,18 +23511,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23558,22 +23530,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23582,11 +23554,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23596,11 +23568,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23610,11 +23582,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23622,11 +23594,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23637,11 +23609,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23649,11 +23621,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23661,11 +23633,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23675,11 +23647,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23687,11 +23659,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23699,11 +23671,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23711,11 +23683,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23724,11 +23696,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23737,11 +23709,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23751,7 +23723,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23759,69 +23731,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23829,48 +23801,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23881,7 +23853,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23891,17 +23863,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23910,14 +23882,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23928,7 +23900,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23936,30 +23908,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23967,30 +23939,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23998,60 +23970,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24060,79 +24032,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24141,7 +24113,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24149,7 +24121,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24159,21 +24131,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24181,7 +24153,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24190,7 +24162,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24200,14 +24172,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24216,28 +24188,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24246,27 +24218,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24276,7 +24248,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24286,13 +24258,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24512,7 +24484,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24520,7 +24492,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24531,15 +24503,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24547,7 +24519,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24555,7 +24527,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24567,43 +24539,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24612,23 +24584,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/pl/LC_MESSAGES/messages.po b/locales/pl/LC_MESSAGES/messages.po index bb7f40807..c3e1a2c8e 100644 --- a/locales/pl/LC_MESSAGES/messages.po +++ b/locales/pl/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-04-17 21:06+0000\n" "Last-Translator: Stan Ulbrych \n" "Language-Team: Polish `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8564,7 +8564,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8589,79 +8589,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8635,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8644,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13580,7 +13546,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23031,7 +22997,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23503,7 +23469,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23513,28 +23485,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23545,18 +23517,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23564,22 +23536,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23588,11 +23560,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23602,11 +23574,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23616,11 +23588,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23628,11 +23600,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23643,11 +23615,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23655,11 +23627,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23667,11 +23639,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23681,11 +23653,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23693,11 +23665,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23705,11 +23677,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23717,11 +23689,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23730,11 +23702,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23743,11 +23715,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23757,7 +23729,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23765,69 +23737,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23835,48 +23807,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23887,7 +23859,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23897,17 +23869,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23916,14 +23888,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23934,7 +23906,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23942,30 +23914,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23973,30 +23945,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24004,60 +23976,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24066,79 +24038,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24147,7 +24119,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24155,7 +24127,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24165,21 +24137,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24187,7 +24159,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24196,7 +24168,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24206,14 +24178,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24222,28 +24194,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24252,27 +24224,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24282,7 +24254,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24292,13 +24264,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24518,7 +24490,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24526,7 +24498,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24537,15 +24509,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24553,7 +24525,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24561,7 +24533,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24573,43 +24545,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24618,23 +24590,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/pt_BR/LC_MESSAGES/messages.po b/locales/pt_BR/LC_MESSAGES/messages.po index 45404d68c..7c7836989 100644 --- a/locales/pt_BR/LC_MESSAGES/messages.po +++ b/locales/pt_BR/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-04-14 02:01+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Portuguese (Brazil) `, you may need to " +#| "provide a username/password combination." +msgid "" +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -10952,11 +10963,18 @@ msgstr "" "fornecer uma combinação de nome de usuário/senha." #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:35 +#, fuzzy +#| msgid "" +#| "Since this guide will demonstrate uploading to both PyPI and TestPyPI, " +#| "we'll need two trusted publishers configured. The following steps will " +#| "lead you through creating the \"pending\" publishers for your new :term:" +#| "`PyPI project `. However it is also possible to add `trusted " +#| "publishing`_ to any pre-existing project, if you are its owner." msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" "Como este guia demonstrará o envio para PyPI e TestPyPI, precisaremos de " @@ -11112,6 +11130,15 @@ msgid "Defining a workflow job environment" msgstr "Definindo um ambiente de tarefa do fluxo de trabalho" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:130 +#, fuzzy +#| msgid "" +#| "Now, let's add initial setup for our job that will publish to PyPI. It's " +#| "a process that will execute commands that we'll define later. In this " +#| "guide, we'll use the latest stable Ubuntu LTS version provided by GitHub " +#| "Actions. This also defines a GitHub Environment for the job to run in its " +#| "context and a URL to be displayed in GitHub's UI nicely. Additionally, it " +#| "allows acquiring an OpenID Connect token that the ``pypi-publish`` " +#| "actions needs to implement secretless trusted publishing to PyPI." msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -11119,7 +11146,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" "Agora, vamos adicionar a configuração inicial para nosso trabalho que será " "publicado no PyPI. É um processo que executará comandos que definiremos mais " @@ -11158,74 +11185,19 @@ msgstr "" "`download-artifact`_, ele envia o conteúdo da pasta ``dist /`` para PyPI " "incondicionalmente." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "Assinando os pacotes de distribuição" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -"O trabalho a seguir assina os pacotes de distribuição com `Sigstore`_, o " -"mesmo sistema de assinatura de artefato `usado para assinar o CPython " -"`_." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" -"Em primeiro lugar, ele usa `sigstore/gh-action-sigstore-python do GitHub " -"Action`_ para assinar os pacotes de distribuição. Na próxima etapa, uma " -"versão vazia do GitHub da tag atual é criada usando a CLI ``gh``. Observe " -"que esta etapa pode ser ainda mais personalizada. Consulte a `documentação " -"de lançamento do gh `_ como " -"referência." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" -"Pode ser necessário gerenciar suas permissões do ``GITHUB_TOKEN`` para " -"permitir a criação da versão do GitHub. Consulte a `documentação do GitHub " -"`_ para obter instruções. Especificamente, o token precisa da " -"permissão ``contents: write``." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" -"Finalmente, as distribuições assinadas são enviadas para o GitHub Release." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" -"Este é um substituto para assinaturas GPG, para as quais o suporte foi " -"`removido do PyPI `_. " -"No entanto, este trabalho não é obrigatório para o envio para PyPI e pode " -"ser omitido." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "Fluxo de trabalho separado para publicação no TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11233,7 +11205,7 @@ msgstr "" "Agora, repita essas etapas e crie outro trabalho para publicação no índice " "do pacote TestPyPI na seção ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11244,21 +11216,21 @@ msgstr "" "branch principal e é frequentemente usado para indicar um pipeline de " "publicação de lançamento íntegro." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "O fluxo de trabalho de CI/CD completo" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "Este parágrafo mostra todo o fluxo de trabalho após seguir o guia acima." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "Isso é tudo, pessoal!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11271,7 +11243,7 @@ msgstr "" "construções de teste para seus usuários alfa, bem como garantir que sua " "versão pipeline permaneça saudável!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11286,7 +11258,7 @@ msgstr "" "um servidor compatível com PyPI como :ref:`pypiserver` no CI para fins de " "teste." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -17777,7 +17749,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "Histórico" @@ -28763,7 +28735,7 @@ msgstr "" "conforme originalmente especificado na :pep:`508`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "Especificadores de versão" @@ -29242,7 +29214,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -29252,29 +29230,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "Versões" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -29285,18 +29263,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "Normalização" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -29304,23 +29282,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "Sensível a maiúsculas e minúsculas" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "Normalização" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -29329,12 +29307,12 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 #, fuzzy msgid "Pre-release separators" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -29344,12 +29322,12 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 #, fuzzy msgid "Pre-release spelling" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -29359,11 +29337,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "Número de pré-lançamento implícito" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -29371,11 +29349,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "Separadores de pós lançamento" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -29386,12 +29364,12 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 #, fuzzy msgid "Post release spelling" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -29399,11 +29377,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "Número implícito de pós lançamento" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -29411,11 +29389,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "Pós lançamentos implícitos" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -29425,11 +29403,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "Separadores de versões de desenvolvimento" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -29437,11 +29415,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "Número implícito de versão de desenvolvimento" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -29449,12 +29427,12 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 #, fuzzy msgid "Local version segments" msgstr "Identificadores de versão local" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -29462,11 +29440,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "Caractere predecessor v" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -29475,11 +29453,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -29488,12 +29466,12 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 #, fuzzy msgid "Examples of compliant version schemes" msgstr "Aqui estão alguns exemplos de números de versão compatíveis::" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -29503,7 +29481,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -29511,70 +29489,70 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 #, fuzzy msgid "Simple \"major.minor\" versioning::" msgstr "Versionamento serial" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "Versionamento simples \"major.minor.micro\" ::" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -29582,48 +29560,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "Ordenação de versões em diferentes versões de metadados" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -29634,7 +29612,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -29644,18 +29622,18 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 #, fuzzy msgid "Compatibility with other version schemes" msgstr "Lidando com os wheels universais" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -29664,14 +29642,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -29682,7 +29660,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -29690,31 +29668,31 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 #, fuzzy msgid "DVCS based version labels" msgstr "Versionamento baseado em data" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -29722,31 +29700,31 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 #, fuzzy msgid "Olson database versioning" msgstr "Versionamento baseado em data" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -29754,60 +29732,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: `Compatible release`_ clause" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "``==``: `Version matching`_ clause" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: `Version exclusion`_ clause" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "``<``, ``>``: `Exclusive ordered comparison`_ clause" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: `Arbitrary equality`_ clause." -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -29816,81 +29794,81 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "Versão compatível" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 #, fuzzy msgid "For example, the following groups of version clauses are equivalent::" msgstr "Isso significa que os seguintes nomes são todos equivalentes:" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 #, fuzzy msgid "Version matching" msgstr "Versão" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -29899,7 +29877,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -29907,7 +29885,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -29917,21 +29895,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -29939,7 +29917,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -29948,7 +29926,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -29958,14 +29936,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -29974,29 +29952,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "Especificador de Versão" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "Comparação ordenada inclusiva" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -30005,27 +29983,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "Comparação ordenada exclusiva" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -30035,7 +30013,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -30045,13 +30023,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -30280,7 +30258,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -30288,7 +30266,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -30299,17 +30277,17 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 #, fuzzy msgid "Remote URL examples::" msgstr "Por exemplo::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 #, fuzzy msgid "File URLs" msgstr "URLs de arquivos" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -30317,7 +30295,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -30325,7 +30303,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -30337,43 +30315,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "Resumo das diferenças em relação a pkg_resources.parse_version" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -30382,23 +30360,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 #, fuzzy msgid "Python Virtual Environments" @@ -32585,6 +32569,65 @@ msgid "" "the file is empty)." msgstr "" +#~ msgid "Signing the distribution packages" +#~ msgstr "Assinando os pacotes de distribuição" + +#~ msgid "" +#~ "The following job signs the distribution packages with `Sigstore`_, the " +#~ "same artifact signing system `used to sign CPython `_." +#~ msgstr "" +#~ "O trabalho a seguir assina os pacotes de distribuição com `Sigstore`_, o " +#~ "mesmo sistema de assinatura de artefato `usado para assinar o CPython " +#~ "`_." + +#~ msgid "" +#~ "Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ " +#~ "to sign the distribution packages. In the next step, an empty GitHub " +#~ "Release from the current tag is created using the ``gh`` CLI. Note this " +#~ "step can be further customised. See the `gh release documentation " +#~ "`_ as a reference." +#~ msgstr "" +#~ "Em primeiro lugar, ele usa `sigstore/gh-action-sigstore-python do GitHub " +#~ "Action`_ para assinar os pacotes de distribuição. Na próxima etapa, uma " +#~ "versão vazia do GitHub da tag atual é criada usando a CLI ``gh``. Observe " +#~ "que esta etapa pode ser ainda mais personalizada. Consulte a " +#~ "`documentação de lançamento do gh `_ como referência." + +#~ msgid "" +#~ "You may need to manage your ``GITHUB_TOKEN`` permissions to enable " +#~ "creating the GitHub Release. See the `GitHub documentation `_ for " +#~ "instructions. Specifically, the token needs the ``contents: write`` " +#~ "permission." +#~ msgstr "" +#~ "Pode ser necessário gerenciar suas permissões do ``GITHUB_TOKEN`` para " +#~ "permitir a criação da versão do GitHub. Consulte a `documentação do " +#~ "GitHub `_ para obter instruções. Especificamente, o " +#~ "token precisa da permissão ``contents: write``." + +#~ msgid "" +#~ "Finally, the signed distributions are uploaded to the GitHub Release." +#~ msgstr "" +#~ "Finalmente, as distribuições assinadas são enviadas para o GitHub Release." + +#~ msgid "" +#~ "This is a replacement for GPG signatures, for which support has been " +#~ "`removed from PyPI `_. However, this job is not mandatory for uploading to PyPI and can be " +#~ "omitted." +#~ msgstr "" +#~ "Este é um substituto para assinaturas GPG, para as quais o suporte foi " +#~ "`removido do PyPI `_. No entanto, este trabalho não é obrigatório para o envio para PyPI e " +#~ "pode ser omitido." + #, fuzzy #~| msgid "" #~| "This can take two forms. You can put your license in a file, typically " diff --git a/locales/ro/LC_MESSAGES/messages.po b/locales/ro/LC_MESSAGES/messages.po index 260554f32..132f235fa 100644 --- a/locales/ro/LC_MESSAGES/messages.po +++ b/locales/ro/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2021-08-20 01:32+0000\n" "Last-Translator: GUILHERME FERNANDES NETO \n" "Language-Team: Romanian `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8563,7 +8563,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8588,79 +8588,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8668,7 +8634,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8677,7 +8643,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13579,7 +13545,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23030,7 +22996,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23502,7 +23468,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23512,28 +23484,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23544,18 +23516,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23563,22 +23535,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23587,11 +23559,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23601,11 +23573,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23615,11 +23587,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23627,11 +23599,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23642,11 +23614,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23654,11 +23626,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23666,11 +23638,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23680,11 +23652,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23692,11 +23664,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23704,11 +23676,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23716,11 +23688,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23729,11 +23701,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23742,11 +23714,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23756,7 +23728,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23764,69 +23736,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23834,48 +23806,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23886,7 +23858,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23896,17 +23868,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23915,14 +23887,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23933,7 +23905,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23941,30 +23913,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23972,30 +23944,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24003,60 +23975,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24065,79 +24037,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24146,7 +24118,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24154,7 +24126,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24164,21 +24136,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24186,7 +24158,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24195,7 +24167,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24205,14 +24177,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24221,28 +24193,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24251,27 +24223,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24281,7 +24253,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24291,13 +24263,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24517,7 +24489,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24525,7 +24497,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24536,15 +24508,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24552,7 +24524,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24560,7 +24532,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24572,43 +24544,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24617,23 +24589,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/ru/LC_MESSAGES/messages.po b/locales/ru/LC_MESSAGES/messages.po index 5c9772206..353e022cf 100644 --- a/locales/ru/LC_MESSAGES/messages.po +++ b/locales/ru/LC_MESSAGES/messages.po @@ -14,8 +14,8 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" -"PO-Revision-Date: 2025-02-26 06:29+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" +"PO-Revision-Date: 2025-05-05 03:01+0000\n" "Last-Translator: gfbdrgn \n" "Language-Team: Russian \n" @@ -25,7 +25,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " "n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" -"X-Generator: Weblate 5.10.2-dev\n" +"X-Generator: Weblate 5.12-dev\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -999,18 +999,16 @@ msgstr "" "рекомендуется." #: ../source/discussions/downstream-packaging.rst:5 -#, fuzzy -#| msgid "Operating system packages" msgid "Supporting downstream packaging" -msgstr "Пакетов операционной системы" +msgstr "Поддержка последующей упаковки" #: ../source/discussions/downstream-packaging.rst:7 msgid "Draft" -msgstr "" +msgstr "Черновик" #: ../source/discussions/downstream-packaging.rst:8 msgid "2025-?" -msgstr "" +msgstr "2025-?" #: ../source/discussions/downstream-packaging.rst:10 msgid "" @@ -1024,6 +1022,16 @@ msgid "" "as native integration with a specific operating system, or assured " "compatibility with specific versions of non-Python software." msgstr "" +"Хотя PyPI и инструменты для упаковки Python, такие как :ref:`pip`, являются " +"основными средствами распространения пакетов Python, они также часто " +"становятся доступными в рамках других экосистем упаковки. Эти усилия по " +"переупаковке в совокупности называются *downstream* упаковкой (ваши " +"собственные усилия называются *upstream* упаковкой), и включают такие " +"проекты, как дистрибутивы Linux, Conda, Homebrew и MacPorts. Как правило, " +"они направлены на улучшение поддержки тех случаев, которые не могут быть " +"решены только средствами упаковки Python, например, интеграция с конкретной " +"операционной системой или обеспечение совместимости с определенными версиями " +"программ, не относящихся к Python." #: ../source/discussions/downstream-packaging.rst:19 msgid "" @@ -1039,6 +1047,19 @@ msgid "" "for different downstreams to carry and keep rebasing the same patches, and " "the risk of applying inconsistent solutions to the same problem." msgstr "" +"В этом обсуждении мы попытаемся объяснить, как обычно выполняется " +"последующая упаковка, и с какими дополнительными проблемами обычно " +"сталкиваются разработчики последующей упаковки. Цель обсуждения - " +"предоставить некоторые необязательные рекомендации, которым могут следовать " +"сопровождающие проекта, чтобы облегчить *значительно* процесс последующей " +"упаковки (не налагая при этом никаких серьезных проблем с обслуживанием на " +"upstream-проект). Обратите внимание, что это не предложение \"все или " +"ничего\" - все, что могут сделать сопровождающие upstream, будет полезно, " +"даже если это лишь малая часть. Нисходящие сопровождающие также готовы " +"подготовить патчи для решения этих проблем. Слияние этих патчей может быть " +"очень полезным, так как это избавит разные нисходящие потоки от " +"необходимости нести и постоянно переиздавать одни и те же патчи, а также от " +"риска применения непоследовательных решений одной и той же проблемы." #: ../source/discussions/downstream-packaging.rst:31 msgid "" @@ -1053,6 +1074,18 @@ msgid "" "regularly active in ensuring the packages they redistribute are updated for " "any compatibility issues that arise when a new Python version is released." msgstr "" +"Установление хороших отношений между разработчиками программного обеспечения " +"и разработчиками пакетов может принести взаимную выгоду. Поставщики часто " +"готовы поделиться своим опытом, временем и оборудованием для улучшения " +"вашего пакета. Иногда они лучше видят, как ваш пакет используется на " +"практике, и могут предоставить информацию о его связях с другими пакетами, " +"получение которой в противном случае потребовало бы значительных усилий. " +"Упаковщики часто могут найти ошибки до того, как ваши пользователи начнут их " +"использовать в производстве, предоставляют отчеты об ошибках хорошего " +"качества и поставляют исправления, когда это возможно. Например, они " +"регулярно следят за тем, чтобы пакеты, которые они распространяют, " +"обновлялись для решения проблем совместимости, возникающих при выходе новой " +"версии Python." #: ../source/discussions/downstream-packaging.rst:43 msgid "" @@ -3352,7 +3385,7 @@ msgstr "" "изменения." #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "Семантическая версификация" @@ -5026,7 +5059,7 @@ msgstr "Описание" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "Примеры" @@ -11099,12 +11132,23 @@ msgstr "" "`cibuildwheel`." #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +#, fuzzy +#| msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "Настройка доверенной публикации" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 -msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +#, fuzzy +#| msgid "" +#| "This guide relies on PyPI's `trusted publishing`_ implementation to " +#| "connect to `GitHub Actions CI/CD`_. This is recommended for security " +#| "reasons, since the generated tokens are created for each of your projects " +#| "individually and expire automatically. Otherwise, you'll need to generate " +#| "an `API token`_ for both PyPI and TestPyPI. In case of publishing to " +#| "third-party indexes like :doc:`devpi `, you may need to " +#| "provide a username/password combination." +msgid "" +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -11121,11 +11165,18 @@ msgstr "" "может потребоваться указать комбинацию имя пользователя/пароль." #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:35 +#, fuzzy +#| msgid "" +#| "Since this guide will demonstrate uploading to both PyPI and TestPyPI, " +#| "we'll need two trusted publishers configured. The following steps will " +#| "lead you through creating the \"pending\" publishers for your new :term:" +#| "`PyPI project `. However it is also possible to add `trusted " +#| "publishing`_ to any pre-existing project, if you are its owner." msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" "Поскольку в этом руководстве мы продемонстрируем загрузку на PyPI и " @@ -11278,6 +11329,15 @@ msgid "Defining a workflow job environment" msgstr "Определение рабочей среды рабочего процесса" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:130 +#, fuzzy +#| msgid "" +#| "Now, let's add initial setup for our job that will publish to PyPI. It's " +#| "a process that will execute commands that we'll define later. In this " +#| "guide, we'll use the latest stable Ubuntu LTS version provided by GitHub " +#| "Actions. This also defines a GitHub Environment for the job to run in its " +#| "context and a URL to be displayed in GitHub's UI nicely. Additionally, it " +#| "allows acquiring an OpenID Connect token that the ``pypi-publish`` " +#| "actions needs to implement secretless trusted publishing to PyPI." msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -11285,7 +11345,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" "Теперь давайте добавим начальную настройку для нашего задания, которое будет " "публиковаться в PyPI. Это процесс, который будет выполнять команды, которые " @@ -11324,70 +11384,19 @@ msgstr "" "загрузки сохраненного дистрибутива действием `download-artifact`_, оно " "безусловно загружает содержимое папки ``dist/`` в PyPI." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "Подписание пакетов распространения" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" -"Следующее задание подписывает пакеты дистрибутива с помощью `Sigstore`_, той " -"же системы подписи артефактов, которая `использовалась для подписи CPython " -"`_." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" -"Сначала используется GitHub Action `sigstore/gh-action-sigstore-python`_ для " -"подписи дистрибутивных пакетов. На следующем этапе с помощью ``gh`` CLI " -"создается пустой GitHub Release из текущего тега. Обратите внимание, что " -"этот шаг может быть дополнительно настроен. См. документацию `gh release " -"`_ в качестве ссылки." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" -"Вам может потребоваться изменить права ``GITHUB_TOKEN``, чтобы разрешить " -"создание релиза GitHub. Инструкции см. в документации по GitHub `_. В частности, " -"токену необходимо разрешение ``содержимое: запись``." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "Наконец, подписанные дистрибутивы загружаются на GitHub Release." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -"Это замена для подписей GPG, поддержка которых была `удалена из PyPI " -"`_. Тем не менее, это " -"задание не является обязательным для загрузки в PyPI и может быть пропущено." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "Отдельный рабочий процесс для публикации в TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11395,7 +11404,7 @@ msgstr "" "Теперь повторите эти шаги и создайте еще одно задание для публикации в " "индекс пакета TestPyPI в разделе ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11406,22 +11415,22 @@ msgstr "" "основной ветке и часто используется для обозначения здорового конвейера " "публикации pipрелизов." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "Весь рабочий процесс CI/CD" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "В этом пункте показан весь рабочий процесс после выполнения вышеописанного " "руководства." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "Вот и все, друзья!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11434,7 +11443,7 @@ msgstr "" "сборок вашим альфа-пользователям, а также для того, чтобы убедиться, что ваш " "конвейер релизовpip остаётся здоровым!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11448,7 +11457,7 @@ msgstr "" "увеличен, но лучшим решением может быть использование PyPI-совместимого " "сервера, например :ref:`pypiserver`, в CI для тестирования." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -18006,7 +18015,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "История" @@ -30470,7 +30479,7 @@ msgstr "" "было стандартизировано с помощью :pep:`639`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "Спецификаторы версии" @@ -31131,7 +31140,18 @@ msgid "" msgstr "" "Релизы разработки также разрешены для предварительных и последующих релизов::" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +#, fuzzy +#| msgid "" +#| "Developmental releases are also permitted for pre-releases and post-" +#| "releases::" +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" +"Релизы разработки также разрешены для предварительных и последующих релизов::" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -31147,7 +31167,7 @@ msgstr "" "вместо этого создать новый предварительный релиз, увеличив числовой " "компонент." -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " @@ -31158,11 +31178,11 @@ msgstr "" "release для полных релизов сопровождения, которые могут включать изменения " "кода." -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "Эпохи версий" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" @@ -31171,11 +31191,11 @@ msgstr "" "остальными компонентами и отделяется от сегмента релиза восклицательным " "знаком::" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "Если явная эпоха не указана, то неявной эпохой будет ``0``." -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -31193,7 +31213,7 @@ msgstr "" "как ``1.0``, то новые релизы будут идентифицироваться как *более старые*, " "чем версии, основанные на дате, при использовании обычной схемы сортировки::" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " @@ -31203,11 +31223,11 @@ msgstr "" "сортировки: все версии, относящиеся к более поздней эпохе, будут " "отсортированы после версий, относящихся к более ранней эпохе::" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "Нормализация" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -31219,11 +31239,11 @@ msgstr "" "версий. Эти синтаксисы ДОЛЖНЫ учитываться при разборе версии, однако они " "должны быть \"нормализованы\" к стандартному синтаксису, определенному выше." -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "Чувствительность случая" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " @@ -31234,11 +31254,11 @@ msgstr "" "использовать такие версии, как ``1.1RC1``, которые будут нормализованы до " "``1.1rc1``." -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "Нормализация целого числа" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -31253,11 +31273,11 @@ msgstr "" "версии, например ``1.0+foo0100``, которая уже находится в нормализованной " "форме." -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "Сепараторы перед выпуском" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -31274,11 +31294,11 @@ msgstr "" "release и цифрой. Это позволяет использовать такие версии, как ``1.0a.1``, " "которые будут нормализованы до ``1.0a1``." -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "Предварительное написание" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -31294,11 +31314,11 @@ msgstr "" "``1.1a1``, ``1.1b2`` и ``1.1rc3``. В каждом случае дополнительные написания " "следует считать эквивалентными их нормальным формам." -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "Неявный номер предварительного выпуска" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -31310,11 +31330,11 @@ msgstr "" "``0``. Это позволяет использовать такие версии, как ``1.2a``, которые " "нормализуются до ``1.2a0``." -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "Сепараторы после выпуска" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -31332,11 +31352,11 @@ msgstr "" "обозначением пострелиза и цифрой. Это позволяет использовать версии типа " "``1.2.post-2``, которые нормализуются до ``1.2.post2``." -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "Написание после выпуска" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -31348,11 +31368,11 @@ msgstr "" "до ``1.0.post4``. Как и в предыдущих версиях, дополнительные написания " "следует считать эквивалентными их нормальным формам." -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "Неявный номер после выпуска" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -31364,11 +31384,11 @@ msgstr "" "позволяет использовать такие версии, как ``1.2.post``, которые нормализуются " "до ``1.2.post0``." -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "Неявные пост-релизы" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -31385,11 +31405,11 @@ msgstr "" "словами, ``1.0-`` - это *не* допустимая версия, и она *не* нормализуется до " "``1.0.post0``." -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "Сепараторы для выпуска продукции" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -31401,11 +31421,11 @@ msgstr "" "``.``. Это позволяет использовать такие версии, как ``1.2-dev2`` или " "``1.2dev2``, которые нормализуются до ``1.2.dev2``." -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "Номер выпуска неявной разработки" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -31417,11 +31437,11 @@ msgstr "" "``0``. Это позволяет использовать такие версии, как ``1.2.dev``, которые " "нормализуются до ``1.2.dev0``." -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "Сегменты локальной версии" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -31433,11 +31453,11 @@ msgstr "" "является использование символа ``.``. Это позволяет нормализовать такие " "версии, как ``1.0+ubuntu-1``, до ``1.0+ubuntu.1``." -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "Предшествующий символ v" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -31450,11 +31470,11 @@ msgstr "" "целей и должен быть опущен во всех нормализованных формах версии. Одна и та " "же версия с ``v`` и без него считается эквивалентной." -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "Ведущие и отслеживающие Белое пространство" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -31468,11 +31488,11 @@ msgstr "" "обрабатывать случайные пробелы, например, версия ``1.0\\n`` нормализуется до " "``1.0``." -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "Примеры совместимых схем версий" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -31488,7 +31508,7 @@ msgstr "" "относительный порядок версий, хотя приведенные выше правила гарантируют, что " "все совместимые инструменты будут упорядочивать их последовательно." -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -31500,22 +31520,22 @@ msgstr "" "гарантируя, что \"последний релиз\" и \"последний стабильный релиз\" могут " "быть легко определены как людьми, так и автоматизированными инструментами." -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "Простая версификация \"major.minor\" ::" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "Простая версия \"major.minor.micro\" ::" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" "Версии \"major.minor\" с предварительными выпусками альфа-версий, бета-" "версий и кандидатов::" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" @@ -31523,7 +31543,7 @@ msgstr "" "«major.minor»-версия с релизами, кандидатами на выпуск и пост-релизами для " "незначительных исправлений ::" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" @@ -31531,11 +31551,11 @@ msgstr "" "Релизы, основанные на дате, с использованием возрастающей серии в пределах " "каждого года, пропуская нулевой::" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "Краткое описание разрешенных суффиксов и относительного порядка" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " @@ -31545,7 +31565,7 @@ msgstr "" "автоматически обрабатывающих метаданные дистрибутива, а не для разработчиков " "дистрибутивов Python, принимающих решение о выборе схемы версионирования." -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " @@ -31555,7 +31575,7 @@ msgstr "" "соответствии с числовым значением данной эпохи. Если сегмент эпохи " "отсутствует, неявное числовое значение равно ``0``." -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " @@ -31565,7 +31585,7 @@ msgstr "" "порядке, что и сортировка кортежей в Python, когда нормализованный сегмент " "выпуска разбирается следующим образом::" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." @@ -31573,7 +31593,7 @@ msgstr "" "Все сегменты релиза, участвующие в сравнении, ДОЛЖНЫ быть приведены к единой " "длине путем заполнения более коротких сегментов нулями по мере необходимости." -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" @@ -31581,7 +31601,7 @@ msgstr "" "В числовом выпуске (``1.0``, ``2.7.3``) разрешены следующие суффиксы, " "которые ДОЛЖНЫ быть упорядочены, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -31594,7 +31614,7 @@ msgstr "" "в одном сегменте выпуска как неоднозначный и остаться в соответствии со " "спецификацией." -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " @@ -31604,7 +31624,7 @@ msgstr "" "(``1.0rc1``, ``1.0c1``) разрешены следующие суффиксы, которые ДОЛЖНЫ быть " "упорядочены, как показано::" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" @@ -31612,7 +31632,7 @@ msgstr "" "Внутри пост-релиза (``1.0.post1``) разрешены следующие суффиксы, которые " "ДОЛЖНЫ быть упорядочены, как показано::" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." @@ -31622,7 +31642,7 @@ msgstr "" "точка, даже если они используются сразу после числовой версии (например, " "``1.0.dev456``, ``1.0.post1``)." -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." @@ -31631,15 +31651,15 @@ msgstr "" "префиксом упорядочивание ДОЛЖНО осуществляться по значению числового " "компонента." -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "Следующий пример охватывает многие из возможных комбинаций::" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "Упорядочивание версий в различных версиях метаданных" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" @@ -31649,7 +31669,7 @@ msgstr "" "стандартную схему идентификации или упорядочивания версий. Однако в " "метаданных v1.2 (:pep:`345`) указана схема, которая определена в :pep:`386`." -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -31666,7 +31686,7 @@ msgstr "" "установить. Эти требования обуславливают необходимость стандартизации одного " "механизма разбора, который будет использоваться для всех версий проекта." -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -31682,7 +31702,7 @@ msgstr "" "и упорядочивания версий, определенным реализацией, если версии, " "соответствующие этой спецификации, недоступны." -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." @@ -31690,11 +31710,11 @@ msgstr "" "Пользователи дистрибутива могут захотеть явно удалить несоответствующие " "версии из всех частных индексов пакетов, которые они контролируют." -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "Совместимость с другими схемами версий" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -31707,7 +31727,7 @@ msgstr "" "спецификации. В таких случаях версия для конкретного проекта может храниться " "в метаданных, а переведенная публичная версия публикуется в поле версии." -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " @@ -31718,7 +31738,7 @@ msgstr "" "позволяя разработчикам использовать внутреннюю схему версионирования, " "которую они предпочитают для своих проектов." -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -31736,7 +31756,7 @@ msgstr "" "дистрибутивов, а также при публикации дистрибутива, на который полагаются " "другие." -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -31748,7 +31768,7 @@ msgstr "" "полностью совместимы со схемой версий, определенной в данной спецификации, и " "соблюдение этих аспектов приветствуется." -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " @@ -31758,7 +31778,7 @@ msgstr "" "(бабочки - пункт 11), не совместимы с этой спецификацией и не разрешены в " "поле публичной версии." -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " @@ -31769,18 +31789,18 @@ msgstr "" "использование суффикса ``.devN`` для указания соответствующего порядка " "версий." -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" "Информация о конкретной сборке также может быть включена в локальные метки " "версий." -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "Метки версий на базе DVCS" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -31792,7 +31812,7 @@ msgstr "" "идентификатору версии. Поскольку хэши не могут быть надежно упорядочены, " "такие версии не допускаются в поле публичной версии." -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " @@ -31803,18 +31823,18 @@ msgstr "" "публикации, а оригинальная метка, основанная на DVCS, может храниться в " "метаданных проекта." -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" "Идентифицирующая хэш-информация также может быть включена в метки локальных " "версий." -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "Версия базы данных Олсона" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " @@ -31824,7 +31844,7 @@ msgstr "" "базы данных часового пояса Olson: год, за которым следует строчный символ, " "указывающий на версию базы данных в пределах этого года." -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -31836,7 +31856,7 @@ msgstr "" "'<год>a') и увеличивается с каждым последующим обновлением базы данных в " "течение года." -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." @@ -31845,7 +31865,7 @@ msgstr "" "соответствующая версия базы данных Olson может быть записана в метаданных " "проекта." -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" @@ -31853,35 +31873,35 @@ msgstr "" "Спецификатор версии состоит из ряда пунктов версии, разделенных запятыми. " "Например::" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "Оператор сравнения определяет тип положения версии:" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: `Совместимый релиз`_ пункт" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "``==``: `Версия соответствует`_ пункту" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: `исключение версии`_ пункт" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "``<=``, ``>=``: предложение ``включенного упорядоченного сравнения`_" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "``<``, ``>``: предложение ``исключительного упорядоченного сравнения``" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: предложение `произвольного равенства`." -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " @@ -31891,7 +31911,7 @@ msgstr "" "должна соответствовать всем заданным пунктам версии, чтобы соответствовать " "спецификатору в целом." -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." @@ -31899,7 +31919,7 @@ msgstr "" "Пробелы между условным оператором и следующим идентификатором версии " "необязательны, как и пробелы вокруг запятых." -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -31914,7 +31934,7 @@ msgstr "" "кандидатов, ДОЛЖЕН решаться в соответствии с описанием в `Обработке " "предварительных выпусков`_." -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " @@ -31925,11 +31945,11 @@ msgstr "" "ДОЛЖНЫ полностью игнорироваться при проверке соответствия версий-кандидатов " "заданному спецификатору версий." -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "Совместимый выпуск" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " @@ -31939,7 +31959,7 @@ msgstr "" "``~=`` и идентификатора версии. Он соответствует любой версии-кандидату, " "которая, как ожидается, будет совместима с указанной версией." -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " @@ -31949,7 +31969,7 @@ msgstr "" "в `Схема версии`_. Локальные идентификаторы версий в этом спецификаторе " "версий НЕ допускаются." -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" @@ -31957,7 +31977,7 @@ msgstr "" "Для данного идентификатора выпуска ``V.N`` совместимое положение о выпуске " "приблизительно эквивалентно паре положений сравнения::" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." @@ -31965,11 +31985,11 @@ msgstr "" "Этот оператор НЕ ДОЛЖЕН использоваться с номером версии одного сегмента, " "таким как ``~=1``." -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "Например, следующие группы положений о версии эквивалентны::" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " @@ -31979,7 +31999,7 @@ msgstr "" "совместимом релизе как ``V.N.suffix``, то суффикс игнорируется при " "определении требуемого соответствия префикса::" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " @@ -31990,11 +32010,11 @@ msgstr "" "контролироваться путем добавления дополнительных нулей к спецификатору " "версии::" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "Соответствие версий" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." @@ -32002,7 +32022,7 @@ msgstr "" "Условие сопоставления версий включает оператор сопоставления версий ``==`` и " "идентификатор версии." -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " @@ -32012,7 +32032,7 @@ msgstr "" "в `Version scheme`_, но в идентификаторах публичных версий допускается " "наличие конца ``.*``, как описано ниже." -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -32025,7 +32045,7 @@ msgstr "" "Единственная выполняемая замена - это нулевое заполнение сегмента выпуска, " "чтобы гарантировать, что сегменты выпуска сравниваются с одинаковой длиной." -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -32037,7 +32057,7 @@ msgstr "" "ДОЛЖНЫ как минимум выдавать предупреждения, а могут и полностью отклонять " "их, если строгое соответствие версий используется неуместно." -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -32054,8 +32074,8 @@ msgstr "" "то сдерживающие компоненты (или их отсутствие) в сегменте релиза также " "игнорируются." -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" @@ -32063,7 +32083,7 @@ msgstr "" "Например, для версии ``1.1.post1`` следующие пункты будут совпадать или не " "совпадать, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " @@ -32073,7 +32093,7 @@ msgstr "" "подразумеваемый предшествующий ``.``, поэтому, учитывая версию ``1.1a1``, " "следующие фразы будут соответствовать или не соответствовать, как показано::" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -32085,7 +32105,7 @@ msgstr "" "сегмента release в идентификаторах версий). Для версии ``1.1`` следующие " "пункты будут совпадать или не совпадать, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -32100,7 +32120,7 @@ msgstr "" "сравнения, поэтому использование любого из них в префиксном совпадении не " "имеет смысла." -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -32116,7 +32136,7 @@ msgstr "" "при определении зависимостей для повторяющихся *развертываний приложений* " "при использовании общего индекса дистрибутива." -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " @@ -32126,7 +32146,7 @@ msgstr "" "версии (без метки локальной версии), то метка локальной версии любых версий-" "кандидатов ДОЛЖНА игнорироваться при сопоставлении версий." -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -32140,11 +32160,11 @@ msgstr "" "сопоставляется, как описано выше, а метка локальной версии проверяется на " "эквивалентность с помощью строгого сравнения равенства строк." -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "Исключение версии" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." @@ -32152,7 +32172,7 @@ msgstr "" "Предложение об исключении версии включает оператор исключения версии ``!=`` " "и идентификатор версии." -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " @@ -32162,11 +32182,11 @@ msgstr "" "оператора `Version matching`_, за исключением того, что смысл любого " "совпадения инвертируется." -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "Всеобъемлющее упорядоченное сравнение" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -32180,12 +32200,12 @@ msgstr "" "указанной версии с учетом последовательного упорядочивания, определенного " "стандартной `Version scheme`_." -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "Инклюзивные операторы упорядоченного сравнения - ``<=`` и ``>=``." -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." @@ -32193,17 +32213,17 @@ msgstr "" "Как и при сопоставлении версий, сегмент выпуска обнуляется по мере " "необходимости, чтобы сегменты выпуска сравнивались с одинаковой длиной." -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" "Локальные идентификаторы версий в этом спецификаторе версий НЕ допускаются." -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "Исключительное упорядоченное сравнение" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -32219,7 +32239,7 @@ msgstr "" "специально исключают пре-релизы, пост-релизы и локальные версии указанной " "версии." -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -32235,7 +32255,7 @@ msgstr "" "разрешит ``1.7.1``, но не ``1.7.0.post1``, а ``>1.7.post2`` разрешит " "``1.7.1`` и ``1.7.0.post3``, но не ``1.7.0``." -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." @@ -32243,7 +32263,7 @@ msgstr "" "Исключительное упорядоченное сравнение ``>V`` **НЕ ДОЛЖНО** соответствовать " "локальной версии указанной версии." -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " @@ -32539,7 +32559,7 @@ msgstr "" "указано путем включения записи ``=`` в " "качестве части фрагмента URL." -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -32554,7 +32574,7 @@ msgstr "" "МОГУТ не выдавать предупреждения об отсутствии хэшей для систем контроля " "версий, которые не предоставляют идентификаторы фиксации на основе хэшей." -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -32566,7 +32586,7 @@ msgstr "" "добавлена в конец URL с помощью нотации ``@`` или " "``@#``." -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -32583,15 +32603,15 @@ msgstr "" "хэш, чтобы затруднить подделку (создать вредоносное репо с определённым " "тегом легко, а создать репо с определённым *хэшем* - менее)." -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "Примеры удаленных URL::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "URL-адреса файлов" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -32604,7 +32624,7 @@ msgstr "" "определяет путь к файлу в файловой системе, к которому необходимо получить " "доступ." -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -32617,7 +32637,7 @@ msgstr "" "в \\*nix схема ``file://`` может использоваться только для доступа к путям " "на локальной машине." -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -32637,11 +32657,11 @@ msgstr "" "в Windows можно найти в `MSDN `_." -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "Краткое описание отличий от pkg_resources.parse_version" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " @@ -32652,7 +32672,7 @@ msgstr "" "был принят, setuptools 6.0 и более поздние версии приняли описанное здесь " "поведение." -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " @@ -32662,7 +32682,7 @@ msgstr "" "сортировались как большие, чем та же версия без локальной версии, в то время " "как ``pkg_resources.parse_version`` считает это маркером предрелизности." -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " @@ -32672,7 +32692,7 @@ msgstr "" "собой правильную версию, в то время как ``pkg_resources.parse_version`` " "пытается получить некоторое значение из *любой* произвольной строки." -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " @@ -32683,11 +32703,11 @@ msgstr "" "допускает только одно использование каждого типа, и они должны существовать " "в определенном порядке." -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "Приложение: Разбор строк версий с помощью регулярных выражений" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -32701,7 +32721,7 @@ msgstr "" "использовать для проверки того, имеет ли версия уже такую форму, и, если " "нет, извлечь различные компоненты для последующей нормализации." -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" @@ -32709,7 +32729,7 @@ msgstr "" "Чтобы проверить, соответствует ли идентификатор версии каноническому " "формату, можно воспользоваться следующей функцией:" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_):" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "Август 2014 г: Эта спецификация была одобрена через :pep:`440`." +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "Виртуальные среды Python" @@ -34976,6 +35002,63 @@ msgstr "" "Если вы только начинаете с Python упаковки, рекомендуется придерживаться " "*регулярных пакетов* и ``__init__.py`` (даже если файл пуст)." +#~ msgid "Signing the distribution packages" +#~ msgstr "Подписание пакетов распространения" + +#~ msgid "" +#~ "The following job signs the distribution packages with `Sigstore`_, the " +#~ "same artifact signing system `used to sign CPython `_." +#~ msgstr "" +#~ "Следующее задание подписывает пакеты дистрибутива с помощью `Sigstore`_, " +#~ "той же системы подписи артефактов, которая `использовалась для подписи " +#~ "CPython `_." + +#~ msgid "" +#~ "Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ " +#~ "to sign the distribution packages. In the next step, an empty GitHub " +#~ "Release from the current tag is created using the ``gh`` CLI. Note this " +#~ "step can be further customised. See the `gh release documentation " +#~ "`_ as a reference." +#~ msgstr "" +#~ "Сначала используется GitHub Action `sigstore/gh-action-sigstore-python`_ " +#~ "для подписи дистрибутивных пакетов. На следующем этапе с помощью ``gh`` " +#~ "CLI создается пустой GitHub Release из текущего тега. Обратите внимание, " +#~ "что этот шаг может быть дополнительно настроен. См. документацию `gh " +#~ "release `_ в качестве ссылки." + +#~ msgid "" +#~ "You may need to manage your ``GITHUB_TOKEN`` permissions to enable " +#~ "creating the GitHub Release. See the `GitHub documentation `_ for " +#~ "instructions. Specifically, the token needs the ``contents: write`` " +#~ "permission." +#~ msgstr "" +#~ "Вам может потребоваться изменить права ``GITHUB_TOKEN``, чтобы разрешить " +#~ "создание релиза GitHub. Инструкции см. в документации по GitHub `_. В частности, токену необходимо разрешение ``содержимое: " +#~ "запись``." + +#~ msgid "" +#~ "Finally, the signed distributions are uploaded to the GitHub Release." +#~ msgstr "Наконец, подписанные дистрибутивы загружаются на GitHub Release." + +#~ msgid "" +#~ "This is a replacement for GPG signatures, for which support has been " +#~ "`removed from PyPI `_. However, this job is not mandatory for uploading to PyPI and can be " +#~ "omitted." +#~ msgstr "" +#~ "Это замена для подписей GPG, поддержка которых была `удалена из PyPI " +#~ "`_. Тем не менее, " +#~ "это задание не является обязательным для загрузки в PyPI и может быть " +#~ "пропущено." + #~ msgid "" #~ ":pep:`639` (accepted in August 2024) has changed the way the ``license`` " #~ "field is declared. Make sure your preferred build backend supports :pep:" diff --git a/locales/sai/LC_MESSAGES/messages.po b/locales/sai/LC_MESSAGES/messages.po index 2bdcee1de..256e280a7 100644 --- a/locales/sai/LC_MESSAGES/messages.po +++ b/locales/sai/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2713,7 +2713,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "" @@ -3940,7 +3940,7 @@ msgstr "" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "" @@ -8417,12 +8417,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" +msgid "Configuring Trusted Publishing" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -8436,7 +8436,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8555,7 +8555,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8580,79 +8580,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8660,7 +8626,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8669,7 +8635,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13571,7 +13537,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23022,7 +22988,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23494,7 +23460,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23504,28 +23476,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23536,18 +23508,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23555,22 +23527,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23579,11 +23551,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23593,11 +23565,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23607,11 +23579,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23619,11 +23591,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23634,11 +23606,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23646,11 +23618,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23658,11 +23630,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23672,11 +23644,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23684,11 +23656,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23696,11 +23668,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23708,11 +23680,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23721,11 +23693,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23734,11 +23706,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23748,7 +23720,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23756,69 +23728,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23826,48 +23798,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23878,7 +23850,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23888,17 +23860,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23907,14 +23879,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23925,7 +23897,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23933,30 +23905,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23964,30 +23936,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23995,60 +23967,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24057,79 +24029,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24138,7 +24110,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24146,7 +24118,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24156,21 +24128,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24178,7 +24150,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24187,7 +24159,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24197,14 +24169,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24213,28 +24185,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24243,27 +24215,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24273,7 +24245,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24283,13 +24255,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24509,7 +24481,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24517,7 +24489,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24528,15 +24500,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24544,7 +24516,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24552,7 +24524,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24564,43 +24536,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24609,23 +24581,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/si/LC_MESSAGES/messages.po b/locales/si/LC_MESSAGES/messages.po index 2e79da4b6..2ba47ddbe 100644 --- a/locales/si/LC_MESSAGES/messages.po +++ b/locales/si/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2022-06-11 08:19+0000\n" "Last-Translator: Kushan Gunasekera \n" "Language-Team: Sinhala `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8559,7 +8559,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8584,79 +8584,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8664,7 +8630,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8673,7 +8639,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13575,7 +13541,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23026,7 +22992,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23498,7 +23464,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23508,28 +23480,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23540,18 +23512,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23559,22 +23531,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23583,11 +23555,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23597,11 +23569,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23611,11 +23583,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23623,11 +23595,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23638,11 +23610,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23650,11 +23622,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23662,11 +23634,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23676,11 +23648,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23688,11 +23660,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23700,11 +23672,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23712,11 +23684,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23725,11 +23697,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23738,11 +23710,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23752,7 +23724,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23760,69 +23732,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23830,48 +23802,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23882,7 +23854,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23892,17 +23864,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23911,14 +23883,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23929,7 +23901,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23937,30 +23909,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23968,30 +23940,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23999,60 +23971,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24061,79 +24033,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24142,7 +24114,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24150,7 +24122,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24160,21 +24132,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24182,7 +24154,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24191,7 +24163,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24201,14 +24173,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24217,28 +24189,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24247,27 +24219,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24277,7 +24249,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24287,13 +24259,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24513,7 +24485,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24521,7 +24493,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24532,15 +24504,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24548,7 +24520,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24556,7 +24528,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24568,43 +24540,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24613,23 +24585,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index e152d097f..e98a41f09 100644 --- a/locales/sk/LC_MESSAGES/messages.po +++ b/locales/sk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-11-02 00:54+0000\n" "Last-Translator: Milan Šalka \n" "Language-Team: Slovak `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8711,7 +8711,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8736,79 +8736,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8816,7 +8782,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8825,7 +8791,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13735,7 +13701,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23222,7 +23188,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23696,7 +23662,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23706,28 +23678,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23738,18 +23710,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23757,22 +23729,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23781,11 +23753,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23795,11 +23767,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23809,11 +23781,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23821,11 +23793,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23836,11 +23808,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23848,11 +23820,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23860,11 +23832,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23874,11 +23846,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23886,11 +23858,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23898,11 +23870,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23910,11 +23882,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23923,11 +23895,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23936,11 +23908,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23950,7 +23922,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23958,69 +23930,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24028,48 +24000,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24080,7 +24052,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24090,17 +24062,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24109,14 +24081,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24127,7 +24099,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24135,30 +24107,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24166,30 +24138,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24197,60 +24169,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24259,79 +24231,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24340,7 +24312,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24348,7 +24320,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24358,21 +24330,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24380,7 +24352,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24389,7 +24361,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24399,14 +24371,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24415,28 +24387,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24445,27 +24417,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24475,7 +24447,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24485,13 +24457,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24711,7 +24683,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24719,7 +24691,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24730,15 +24702,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24746,7 +24718,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24754,7 +24726,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24766,43 +24738,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24811,23 +24783,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/ta/LC_MESSAGES/messages.po b/locales/ta/LC_MESSAGES/messages.po index f12edb029..386422c76 100644 --- a/locales/ta/LC_MESSAGES/messages.po +++ b/locales/ta/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-02-27 01:55+0000\n" "Last-Translator: தமிழ்நேரம் \n" "Language-Team: Tamil `, you may need to " +#| "provide a username/password combination." +msgid "" +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -10769,11 +10780,18 @@ msgstr "" "வேண்டியிருக்கலாம்." #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:35 +#, fuzzy +#| msgid "" +#| "Since this guide will demonstrate uploading to both PyPI and TestPyPI, " +#| "we'll need two trusted publishers configured. The following steps will " +#| "lead you through creating the \"pending\" publishers for your new :term:" +#| "`PyPI project `. However it is also possible to add `trusted " +#| "publishing`_ to any pre-existing project, if you are its owner." msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" "இந்த வழிகாட்டி PYPI மற்றும் TestPypi இரண்டிலும் பதிவேற்றுவதை நிரூபிக்கும் என்பதால், " @@ -10927,6 +10945,15 @@ msgid "Defining a workflow job environment" msgstr "பணிப்பாய்வு வேலை சூழலை வரையறுத்தல்" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:130 +#, fuzzy +#| msgid "" +#| "Now, let's add initial setup for our job that will publish to PyPI. It's " +#| "a process that will execute commands that we'll define later. In this " +#| "guide, we'll use the latest stable Ubuntu LTS version provided by GitHub " +#| "Actions. This also defines a GitHub Environment for the job to run in its " +#| "context and a URL to be displayed in GitHub's UI nicely. Additionally, it " +#| "allows acquiring an OpenID Connect token that the ``pypi-publish`` " +#| "actions needs to implement secretless trusted publishing to PyPI." msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -10934,7 +10961,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" "இப்போது, எங்கள் வேலைக்கு ஆரம்ப அமைப்பைச் சேர்ப்போம், அது பைபிக்கு வெளியிடப்படும். இது ஒரு " "செயல்முறையாகும், இது நாங்கள் பின்னர் வரையறுக்கும் கட்டளைகளை இயக்கும். இந்த வழிகாட்டியில், " @@ -10972,72 +10999,19 @@ msgstr "" "பிறகு, இது `` மாவட்ட/`கோப்புறையின் உள்ளடக்கங்களை பதிவேற்றுகிறது நிபந்தனையின்றி " "பைபிக்குள்." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "விநியோக தொகுப்புகளில் கையொப்பமிடுதல்" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -"பின்வரும் வேலை விநியோக தொகுப்புகளை `சிக்ச்டோர்`_ உடன் கையொப்பமிடுகிறது, அதே " -"கலைப்பொருள் கையொப்பமிடும் அமைப்பு` cpython `_ இல் கையொப்பமிடப் பயன்படுகிறது." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" -"முதலாவதாக, விநியோக தொகுப்புகளில் கையெழுத்திட இது `சிக்ச்டோர்/சிஎச்-ஆக்சன்-சிக்ச்டோர்-" -"பைதான் அறிவிலிமையம் அதிரடி`_ ஐப் பயன்படுத்துகிறது. அடுத்த கட்டத்தில், தற்போதைய " -"குறிச்சொல்லிலிருந்து வெற்று அறிவிலிமையம் வெளியீடு `` gh`` Cli ஐப் பயன்படுத்தி " -"உருவாக்கப்படுகிறது. இந்த படி மேலும் தனிப்பயனாக்கப்படலாம் என்பதை நினைவில் கொள்க. `சிஎச் " -"வெளியீட்டு ஆவணங்கள் _ _ ஒரு குறிப்பாகப் " -"பார்க்கவும்." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" -"அறிவிலிமையம் வெளியீட்டை உருவாக்க உங்கள் `` github_token`` அனுமதிகளை நிர்வகிக்க " -"வேண்டியிருக்கலாம். `கிட்அப் ஆவணங்கள் `_ அறிவுறுத்தல்களுக்கு. குறிப்பாக, டோக்கனுக்கு `` " -"உள்ளடக்கங்கள்: எழுது `அனுமதி தேவை." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" -"இறுதியாக, கையொப்பமிடப்பட்ட விநியோகங்கள் அறிவிலிமையம் வெளியீட்டில் பதிவேற்றப்படுகின்றன." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" -"இது சிபிசி கையொப்பங்களுக்கு மாற்றாக உள்ளது, இதற்காக பைபி `_ இலிருந்து உதவி அகற்றப்பட்டுள்ளது. இருப்பினும், " -"இந்த வேலை PYPI இல் பதிவேற்றுவதற்கு கட்டாயமில்லை, மேலும் தவிர்க்கப்படலாம்." - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "டெச்ட்பிபிக்கு வெளியிடுவதற்கு பணிப்பாய்வு தனி" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11045,7 +11019,7 @@ msgstr "" "இப்போது, இந்த படிகளை மீண்டும் செய்து, `` வேலைகள்`` பிரிவின் கீழ் டெச்ட்பை தொகுப்பு " "குறியீட்டுக்கு வெளியிட மற்றொரு வேலையை உருவாக்கவும்:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11056,21 +11030,21 @@ msgstr "" "வடிவமைக்கப்பட்டுள்ளது மற்றும் ஆரோக்கியமான வெளியீட்டு வெளியீட்டு குழாய்த்திட்டத்தைக் குறிக்க " "பெரும்பாலும் பயன்படுத்தப்படுகிறது." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "முழு சிஐ/சிடி பணிப்பாய்வு" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "இந்த பத்தி மேலே உள்ள வழிகாட்டியைப் பின்பற்றிய பிறகு முழு பணிப்பாய்வுகளையும் காட்டுகிறது." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "அவ்வளவுதான், எல்லோரும்!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11082,7 +11056,7 @@ msgstr "" "சோதனை கட்டமைப்பை வழங்குவதற்கும், உங்கள் வெளியீட்டு குழாய் ஆரோக்கியமாக இருப்பதை " "உறுதிசெய்வதற்கும் பயனுள்ளதாக இருக்கும் டெச்ட்பிபிக்கு எந்தவொரு உந்துதலையும் வெளியிடும்!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11096,7 +11070,7 @@ msgstr "" "ஒரு சிறந்த தீர்வு ஒரு பைபி-இணக்கமான சேவையகத்தைப் பயன்படுத்தலாம்: குறிப்பு நோக்கங்களுக்காக " "தொஒ இல் `பைபிசெவர்`." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -17506,7 +17480,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "வரலாறு" @@ -29470,7 +29444,7 @@ msgstr "" "`639`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "பதிப்பு விவரக்குறிப்புகள்" @@ -30109,7 +30083,19 @@ msgstr "" "முன் வெளியீடுகள் மற்றும் பிந்தைய வெளியீடுகளுக்கு வளர்ச்சி வெளியீடுகளும் " "அனுமதிக்கப்படுகின்றன ::" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +#, fuzzy +#| msgid "" +#| "Developmental releases are also permitted for pre-releases and post-" +#| "releases::" +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" +"முன் வெளியீடுகள் மற்றும் பிந்தைய வெளியீடுகளுக்கு வளர்ச்சி வெளியீடுகளும் " +"அனுமதிக்கப்படுகின்றன ::" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -30124,7 +30110,7 @@ msgstr "" "வாசகர்களுக்கு அலசுவது கடினம். அத்தகைய வெளியீட்டை வெளியிட வேண்டியிருந்தால், எண் கூறுகளை " "அதிகரிப்பதன் மூலம் புதிய முன் வெளியீட்டை உருவாக்குவது கணிசமாக தெளிவாக உள்ளது." -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " @@ -30134,11 +30120,11 @@ msgstr "" "குறியீடு மாற்றங்களை உள்ளடக்கிய முழு பராமரிப்பு வெளியீடுகளுக்கு வெளியீட்டுக்குப் பிந்தைய " "குறியீட்டைப் பயன்படுத்தும் திட்டங்களுக்கு அவை பொருத்தமானதாக இருக்கலாம்." -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "பதிப்பு சகாப்தங்கள்" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" @@ -30146,12 +30132,12 @@ msgstr "" "பதிப்பு அடையாளங்காட்டியில் சேர்க்கப்பட்டால், சகாப்தம் மற்ற எல்லா கூறுகளுக்கும் முன்பாக " "தோன்றும், வெளியீட்டு பிரிவில் இருந்து ஆச்சரியக் குறி ::" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" "வெளிப்படையான சகாப்தம் எதுவும் கொடுக்கப்படவில்லை என்றால், மறைமுகமான சகாப்தம் `` 0`` ஆகும்." -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -30169,7 +30155,7 @@ msgstr "" "புதிய வெளியீடுகள் சாதாரண வரிசையாக்கத் திட்டத்தைப் பயன்படுத்தும் போது தேதி அடிப்படையிலான " "வெளியீடுகளை விட * பழையவை * என அடையாளம் காணப்படும் ::" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " @@ -30179,11 +30165,11 @@ msgstr "" "முறையில் மாற்ற முடியும், ஏனெனில் முந்தைய சகாப்தத்தின் அனைத்து பதிப்புகளும் முந்தைய " "சகாப்தத்தின் பதிப்புகளுக்குப் பிறகு வரிசைப்படுத்தப்படுகின்றன ::" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "இயல்பாக்கம்" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -30195,11 +30181,11 @@ msgstr "" "ஒரு பதிப்பை பாகுபடுத்தும்போது இந்த தொடரியல் கருத்தில் கொள்ளப்பட வேண்டும், இருப்பினும் அவை " "மேலே வரையறுக்கப்பட்ட நிலையான தொடரியல் க்கு \"இயல்பாக்கப்பட வேண்டும்\"." -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "வழக்கு உணர்திறன்" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " @@ -30209,11 +30195,11 @@ msgstr "" "சாதாரண வடிவம் சிறிய எழுத்துக்கள். இது `` 1.1rc1`` போன்ற பதிப்புகளை அனுமதிக்கிறது, " "இது `1.1rc1`` க்கு இயல்பாக்கப்படும்." -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "முழு எண் இயல்பாக்கம்" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -30227,11 +30213,11 @@ msgstr "" "எண்ணெழுத்து பிரிவின் உள்ளே நுழைவதற்கு இது உண்மையல்ல, இது ஏற்கனவே அதன் இயல்பாக்கப்பட்ட " "வடிவத்தில் உள்ளது." -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "முன் வெளியீட்டு பிரிப்பான்கள்" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -30246,11 +30232,11 @@ msgstr "" "வேண்டும். இது `` 1.0a.1`` போன்ற பதிப்புகளை அனுமதிக்கிறது, இது `` 1.0a1`` க்கு " "இயல்பாக்கப்படும்." -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "முன் வெளியீட்டு எழுத்துப்பிழை" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -30265,11 +30251,11 @@ msgstr "" "`1rc3`` போன்ற பதிப்புகளை அனுமதிக்கிறது. ஒவ்வொரு சந்தர்ப்பத்திலும் கூடுதல் எழுத்துப்பிழை " "அவற்றின் சாதாரண வடிவங்களுக்கு சமமானதாக கருதப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "மறைமுகத்திற்கு முந்தைய வெளியீடு எண்" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -30281,11 +30267,11 @@ msgstr "" "வேண்டும். இது `` 1.2a`` போன்ற பதிப்புகளை அனுமதிக்கிறது, இது `` 1.2A0`` க்கு " "இயல்பாக்கப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "வெளியீட்டு பிரிப்பான்கள் இடுகை" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -30302,11 +30288,11 @@ msgstr "" "அடையாளத்திற்கும் எண்களுக்கும் இடையில் விருப்பமான பிரிப்பான் அனுமதிக்கிறது. இது `` 1.2." "post-2`` போன்ற பதிப்புகளை அனுமதிக்கிறது, இது `` 1.2.post2`` க்கு இயல்பாக்கும்." -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "வெளியீட்டு எழுத்துப்பிழை இடுகை" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -30318,11 +30304,11 @@ msgstr "" "இயல்பாக்குகிறது. முன் வெளியீடுகளைப் போலவே கூடுதல் எழுத்துப்பிழைகள் அவற்றின் சாதாரண " "வடிவங்களுக்கு சமமானதாக கருதப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "மறைமுகமான இடுகை வெளியீட்டு எண்" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -30334,11 +30320,11 @@ msgstr "" "வேண்டும். `` 1.2.post0`` க்கு இயல்பாக்கப்பட்ட `` 1.2.post`` போன்ற பதிப்புகளை இது " "அனுமதிக்கிறது." -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "மறைமுகமான இடுகை வெளியீடுகள்" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -30354,11 +30340,11 @@ msgstr "" "இணைந்து பயன்படுத்தப்படக்கூடாது. வேறு வார்த்தைகளில் கூறுவதானால், `` 1.0 -`` என்பது * " "சரியான பதிப்பாக இல்லை, மேலும் இது * `1.0.post0`` க்கு * இயல்பாக்கப்படாது." -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "வளர்ச்சி வெளியீட்டு பிரிப்பான்கள்" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -30370,11 +30356,11 @@ msgstr "" "பிரிப்பான். இது `` 1.2-DEV2`` அல்லது `1.2dev2`` போன்ற பதிப்புகளை` `1.2.dev2`` க்கு " "இயல்பாக்குகிறது." -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "மறைமுக வளர்ச்சி வெளியீட்டு எண்" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -30386,11 +30372,11 @@ msgstr "" "வேண்டும். `` 1.2.dev0`` க்கு இயல்பாக்கப்பட்ட `` 1.2.dev`` போன்ற பதிப்புகளை இது " "அனுமதிக்கிறது." -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "உள்ளக பதிப்பு பிரிவுகள்" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -30402,11 +30388,11 @@ msgstr "" "எழுத்தைப் பயன்படுத்துகிறது. இது `` 1.0+உபுண்டு -1`` போன்ற பதிப்புகளை `` 1.0+உபுண்டு " "1`` க்கு இயல்பாக்க அனுமதிக்கிறது." -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "V எழுத்து முந்தையது" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -30419,11 +30405,11 @@ msgstr "" "வேண்டும் மற்றும் பதிப்பின் அனைத்து இயல்பாக்கப்பட்ட வடிவங்களிலிருந்தும் தவிர்க்கப்பட வேண்டும். " "`` வி`` உடன் மற்றும் இல்லாமல் அதே பதிப்பு சமமானதாகக் கருதப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "வழிநடத்தும் மற்றும் பின்தங்கிய இடைவெளி" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -30436,11 +30422,11 @@ msgstr "" "மற்றும் `\\ v`` ஆகியவை அடங்கும். `` 1.0 \\ n`` போன்ற பதிப்பு போன்ற தற்செயலான " "இடைவெளியை விவேகத்துடன் கையாள இது அனுமதிக்கிறது, இது `` 1.0`` ஐ இயல்பாக்குகிறது." -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "இணக்கமான பதிப்பு திட்டங்களின் எடுத்துக்காட்டுகள்" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -30456,7 +30442,7 @@ msgstr "" "மேலே உள்ள விதிகள் அனைத்து இணக்கமான கருவிகளும் தொடர்ந்து கட்டளையிடும் என்பதை " "உறுதிசெய்தாலும்." -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -30468,20 +30454,20 @@ msgstr "" "மற்றும் \"அண்மைக் கால நிலையான வெளியீடு\" ஆகியவற்றை மனித பயனர்கள் மற்றும் தானியங்கி " "கருவிகளால் எளிதில் தீர்மானிக்க முடியும் என்பதை உறுதிசெய்கிறது." -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "எளிய \"மேசர்.மினோர்\" பதிப்பு ::" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "எளிய \"மேசர்.மினோர்.மிக்ரோ\" பதிப்பு ::" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "ஆல்பா, பீட்டா மற்றும் வேட்பாளர் முன் வெளியீடுகளுடன் \"மேசர்.மினோர்\" பதிப்பு ::" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" @@ -30489,7 +30475,7 @@ msgstr "" "மேம்பாட்டு வெளியீடுகளுடன் \"மேசர்.மினோர்\" பதிப்பு, வேட்பாளர்கள் மற்றும் சிறிய " "திருத்தங்களுக்கு பிந்தைய வெளியீடுகளை வெளியிடுங்கள் ::" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" @@ -30497,11 +30483,11 @@ msgstr "" "தேதி அடிப்படையிலான வெளியீடுகள், ஒவ்வொரு ஆண்டும் அதிகரிக்கும் சீரியலைப் பயன்படுத்தி, " "பூச்சியத்தைத் தவிர்ப்பது ::" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "அனுமதிக்கப்பட்ட பின்னொட்டுகளின் சுருக்கம் மற்றும் உறவினர் வரிசைப்படுத்தல்" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " @@ -30511,7 +30497,7 @@ msgstr "" "டெவலப்பர்களைக் காட்டிலும், விநியோக மெட்டாடேட்டாவை தானாக செயலாக்கும் கருவிகளின் " "ஆசிரியர்களுக்காக வடிவமைக்கப்பட்டுள்ளது." -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " @@ -30521,7 +30507,7 @@ msgstr "" "வரிசைப்படுத்தப்பட வேண்டும். எபோச் பிரிவு எதுவும் இல்லை என்றால், மறைமுகமான எண் மதிப்பு `` " "0`` ஆகும்." -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " @@ -30531,7 +30517,7 @@ msgstr "" "பின்வருமாறு பாகுபடுத்தப்படும்போது பைதனின் டூப்பிள் வரிசையாக்கத்தின் அதே வரிசையில் " "வரிசைப்படுத்தப்பட வேண்டும் ::" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." @@ -30539,7 +30525,7 @@ msgstr "" "ஒப்பீட்டில் ஈடுபட்டுள்ள அனைத்து வெளியீட்டு பிரிவுகளும் தேவைக்கேற்ப பூச்சியங்களுடன் குறுகிய " "பிரிவுகளைத் திணிப்பதன் மூலம் நிலையான நீளமாக மாற்றப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" @@ -30547,7 +30533,7 @@ msgstr "" "ஒரு எண் வெளியீட்டிற்குள் (`` 1.0``, `` 2.7.3``), பின்வரும் பின்னொட்டுகள் " "அனுமதிக்கப்படுகின்றன, மேலும் காட்டப்பட்டுள்ளபடி ஆர்டர் செய்யப்பட வேண்டும் ::" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -30559,7 +30545,7 @@ msgstr "" "மாதிரியான வெளியீட்டுப் பிரிவில் தெளிவற்ற அதே பிரிவில் ஒரே மாதிரியான` `n`` ஐக் கொண்ட " "வழக்கை கருவிகள் நிராகரிக்கலாம் மற்றும் விவரக்குறிப்புக்கு இணங்க வேண்டும்." -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " @@ -30569,7 +30555,7 @@ msgstr "" "வெளியிடும், பின்வரும் பின்னொட்டுகள் அனுமதிக்கப்படுகின்றன, மேலும் காட்டப்பட்டுள்ளபடி ஆர்டர் " "செய்யப்பட வேண்டும் ::" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" @@ -30577,7 +30563,7 @@ msgstr "" "ஒரு பிந்தைய வெளியீட்டிற்குள் (`` 1.0.post1``), பின்வரும் பின்னொட்டுகள் " "அனுமதிக்கப்படுகின்றன, மேலும் அவை காட்டப்பட்டுள்ளபடி ஆர்டர் செய்யப்பட வேண்டும் ::" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." @@ -30587,7 +30573,7 @@ msgstr "" "பயன்படுத்தும்போது கூட, `` devn`` மற்றும் `` போச்ட்ன்`` எப்போதும் ஒரு புள்ளிக்கு முன்னதாக " "இருக்க வேண்டும் என்பதை நினைவில் கொள்க." -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." @@ -30595,15 +30581,15 @@ msgstr "" "ஒரு முன் வெளியீட்டிற்குள், பகிரப்பட்ட முன்னொட்டுடன் வெளியீடு அல்லது மேம்பாட்டு வெளியீட்டு " "பிரிவுக்குள், வரிசைப்படுத்துதல் எண் கூறுகளின் மதிப்பால் இருக்க வேண்டும்." -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "பின்வரும் எடுத்துக்காட்டு சாத்தியமான பல சேர்க்கைகளை உள்ளடக்கியது ::" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "பதிப்பு வெவ்வேறு மேனிலை தரவு பதிப்புகளில் வரிசைப்படுத்துகிறது" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" @@ -30614,7 +30600,7 @@ msgstr "" "மேனிலை தரவு V1.2 (: PEP: `345`) வரையறுக்கப்பட்ட ஒரு திட்டத்தை குறிப்பிடுகிறது: PEP:" "` 386`." -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -30631,7 +30617,7 @@ msgstr "" "தேவைகள் ஒரு திட்டத்தின் அனைத்து பதிப்புகளுக்கும் பயன்படுத்தப்பட வேண்டிய ஒரு பாகுபடுத்தும் " "பொறிமுறையில் ஒரு தரப்படுத்தல் தேவைப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -30647,7 +30633,7 @@ msgstr "" "கிடைக்கவில்லை என்றால், வரையறுக்கப்பட்ட பதிப்பு பாகுபடுத்தல் மற்றும் வரிசைப்படுத்தும் " "திட்டங்களை செயல்படுத்தலாம்." -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." @@ -30655,11 +30641,11 @@ msgstr "" "விநியோக பயனர்கள் தாங்கள் கட்டுப்படுத்தும் எந்தவொரு தனியார் தொகுப்பு குறியீடுகளிலிருந்தும் " "இணங்காத பதிப்புகளை வெளிப்படையாக அகற்ற விரும்பலாம்." -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "பிற பதிப்பு திட்டங்களுடன் பொருந்தக்கூடிய தன்மை" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -30672,7 +30658,7 @@ msgstr "" "சந்தர்ப்பங்களில், திட்ட குறிப்பிட்ட பதிப்பை மெட்டாடேட்டாவில் சேமிக்க முடியும், அதே நேரத்தில் " "மொழிபெயர்க்கப்பட்ட பொது பதிப்பு பதிப்பு புலத்தில் வெளியிடப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " @@ -30682,7 +30668,7 @@ msgstr "" "வரிசைப்படுத்தலை வழங்க அனுமதிக்கிறது, அதே நேரத்தில் உருவாக்குபவர்கள் தங்கள் திட்டங்களுக்கு " "அவர்கள் விரும்பும் உள் பதிப்பு திட்டத்தைப் பயன்படுத்த அனுமதிக்கிறது." -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -30699,7 +30685,7 @@ msgstr "" "உள்ளடக்கியுள்ளதால், மற்றவர்கள் நம்பியிருக்கும் விநியோகத்தை வெளியிடும் போது இந்த திட்டம் " "புரிந்து கொள்ளத்தக்கது." -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -30711,7 +30697,7 @@ msgstr "" "திட்டத்துடன் முழுமையாக ஒத்துப்போகும், மேலும் இந்த அம்சங்களை பின்பற்றுவது " "ஊக்குவிக்கப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " @@ -30721,7 +30707,7 @@ msgstr "" "பிரிவு 11) கொண்ட சொற்பொருள் பதிப்புகள் * இந்த விவரக்குறிப்புடன் பொருந்தாது மற்றும் பொது " "பதிப்பு துறையில் அனுமதிக்கப்படாது." -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " @@ -30731,16 +30717,16 @@ msgstr "" "மொழிபெயர்ப்பதற்கான ஒரு வழிமுறை, பொருத்தமான பதிப்பு வரிசையைக் குறிப்பிட `` .devn`` " "பின்னொட்டைப் பயன்படுத்துவது." -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "உள்ளக பதிப்பு லேபிள்களிலும் குறிப்பிட்ட உருவாக்க தகவல்கள் சேர்க்கப்படலாம்." -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "டி.வி.சி.எச் அடிப்படையிலான பதிப்பு லேபிள்கள்" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -30752,7 +30738,7 @@ msgstr "" "ஒருங்கிணைக்கின்றன. ஆச்களை நம்பத்தகுந்த வகையில் ஆர்டர் செய்ய முடியாது, இதுபோன்ற பதிப்புகள் " "பொது பதிப்பு துறையில் அனுமதிக்கப்படாது." -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " @@ -30762,16 +30748,16 @@ msgstr "" "வெளியீட்டிற்காக தனித்துவமாக அடையாளம் காண பயன்படுத்தப்படலாம், அதே நேரத்தில் அசல் டி.வி.சி." "எச் அடிப்படையிலான லேபிளை திட்ட மெட்டாடேட்டாவில் சேமிக்க முடியும்." -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "ஆச் தகவல்களை அடையாளம் காண்பது உள்ளக பதிப்பு லேபிள்களிலும் சேர்க்கப்படலாம்." -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "ஓல்சன் தரவுத்தள பதிப்பு" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " @@ -30781,7 +30767,7 @@ msgstr "" "திட்டத்திலிருந்து பெறுகிறது: அந்த ஆண்டுக்குள் தரவுத்தளத்தின் பதிப்பைக் குறிக்கும் சிறிய " "எழுத்து ஆண்டு." -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -30790,7 +30776,7 @@ msgid "" msgstr "" "இதை ஒரு இணக்கமான பொது பதிப்பு அடையாளங்காட்டிக்கு `` <ஆண்டு> என மொழிபெயர்க்கலாம்." -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." @@ -30798,7 +30784,7 @@ msgstr "" "பிற மொழிபெயர்க்கப்பட்ட பதிப்பு அடையாளங்காட்டிகளைப் போலவே, தொடர்புடைய ஓல்சன் தரவுத்தள " "பதிப்பையும் திட்ட மெட்டாடேட்டாவில் பதிவு செய்யலாம்." -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" @@ -30806,35 +30792,35 @@ msgstr "" "ஒரு பதிப்பு விவரக்குறிப்பு தொடர்ச்சியான பதிப்பு உட்பிரிவுகளைக் கொண்டுள்ளது, இது " "காற்புள்ளிகளால் பிரிக்கப்பட்டுள்ளது. உதாரணமாக ::" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "ஒப்பீட்டு ஆபரேட்டர் பதிப்பு விதிமுறையை தீர்மானிக்கிறது:" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "`` ~ = ``: `இணக்கமான வெளியீடு`_ பிரிவு" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "`` == ``: `பதிப்பு பொருந்தும்`_ பிரிவு" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "``! = ``: `பதிப்பு விலக்கு`_ பிரிவு" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "`` <= ``, ``> = ``: `உள்ளடக்கிய உத்தரவிடப்பட்ட ஒப்பீடு`_ பிரிவு" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "`` <``, ``> ``: `பிரத்யேக உத்தரவிடப்பட்ட ஒப்பீடு`_ பிரிவு" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "`` === ``: `தன்னிச்சையான சமத்துவம்`_ பிரிவு." -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " @@ -30843,7 +30829,7 @@ msgstr "" "கமா (\",\") ஒரு தர்க்கரீதியான ** மற்றும் ** ஆபரேட்டருக்கு சமம்: ஒரு வேட்பாளர் பதிப்பு " "கொடுக்கப்பட்ட அனைத்து பதிப்பு உட்பிரிவுகளையும் பொருத்த வேண்டும்." -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." @@ -30851,7 +30837,7 @@ msgstr "" "ஒரு நிபந்தனை ஆபரேட்டருக்கும் பின்வரும் பதிப்பு அடையாளங்காட்டிக்கும் இடையிலான இடைவெளி " "விருப்பமானது, காற்புள்ளிகளைச் சுற்றியுள்ள இடைவெளி." -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -30865,7 +30851,7 @@ msgstr "" "கருதப்படுகிறதா இல்லையா என்பது `முன் வெளியீடுகளை கையாளுதல்`_ இல் விவரிக்கப்பட்டுள்ளபடி " "கையாளப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " @@ -30876,11 +30862,11 @@ msgstr "" "விவரக்குறிப்புடன் பொருந்துமா என்பதைச் சரிபார்க்கும்போது உள்ளக பதிப்பு லேபிள்கள் முற்றிலும் " "புறக்கணிக்கப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "இணக்கமான வெளியீடு" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " @@ -30890,7 +30876,7 @@ msgstr "" "அடையாளங்காட்டியைக் கொண்டுள்ளது. குறிப்பிட்ட பதிப்போடு இணக்கமாக இருக்கும் என்று " "எதிர்பார்க்கப்படும் எந்த வேட்பாளர் பதிப்பையும் இது பொருந்துகிறது." -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " @@ -30900,7 +30886,7 @@ msgstr "" "வடிவத்தில் இருக்க வேண்டும். இந்த பதிப்பு விவரக்குறிப்பில் உள்ளக பதிப்பு அடையாளங்காட்டிகள் " "அனுமதிக்கப்படவில்லை." -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" @@ -30908,18 +30894,18 @@ msgstr "" "கொடுக்கப்பட்ட வெளியீட்டு அடையாளங்காட்டிக்கு `` v.n`` க்கு, இணக்கமான வெளியீட்டு விதிமுறை " "ஒப்பீட்டு உட்பிரிவுகளின் சோடியுக்கு சமமானதாகும் ::" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" "இந்த ஆபரேட்டர் `` ~ = 1`` போன்ற ஒற்றை பிரிவு பதிப்பு எண்ணுடன் பயன்படுத்தப்படக்கூடாது." -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "எடுத்துக்காட்டாக, பதிப்பு உட்பிரிவுகளின் பின்வரும் குழுக்கள் சமமானவை ::" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " @@ -30929,7 +30915,7 @@ msgstr "" "`` v.n.suffix`` என பெயரிடப்பட்டால், தேவையான முன்னொட்டு பொருத்தத்தை தீர்மானிக்கும்போது " "பின்னொட்டு புறக்கணிக்கப்படுகிறது ::" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " @@ -30939,11 +30925,11 @@ msgstr "" "முன்னோக்கி பொருந்தக்கூடிய அளவைக் கருதுவதன் மூலம் கூடுதல் பூச்சியங்களை பதிப்பில் சேர்ப்பதன் " "மூலம் கட்டுப்படுத்த முடியும் ::" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "பதிப்பு பொருந்தும்" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." @@ -30951,7 +30937,7 @@ msgstr "" "ஒரு பதிப்பு பொருந்தும் பிரிவில் பதிப்பு பொருந்தும் ஆபரேட்டர் `` == `` மற்றும் பதிப்பு " "அடையாளங்காட்டி ஆகியவை அடங்கும்." -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " @@ -30961,7 +30947,7 @@ msgstr "" "வடிவத்தில் இருக்க வேண்டும், ஆனால் கீழே விவரிக்கப்பட்டுள்ளபடி பொது பதிப்பு " "அடையாளங்காட்டிகளில்` `." -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -30974,7 +30960,7 @@ msgstr "" "நீளத்துடன் ஒப்பிடப்படுவதை உறுதிசெய்ய வெளியீட்டு பிரிவின் சுழிய திணிப்பு * மட்டுமே " "செய்யப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -30986,7 +30972,7 @@ msgstr "" "வழங்க வேண்டும், மேலும் கடுமையான பதிப்பு போட்டிகள் தகாத முறையில் பயன்படுத்தப்படும்போது " "அவற்றை முழுமையாக நிராகரிக்கலாம்." -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -31002,8 +30988,8 @@ msgstr "" "வெளியீட்டு பிரிவு மட்டுமே இருந்தால், வெளியீட்டு பிரிவில் உள்ள பின்வரும் கூறுகள் (அல்லது " "அதன் பற்றாக்குறை) புறக்கணிக்கப்படுகின்றன." -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" @@ -31011,7 +30997,7 @@ msgstr "" "எடுத்துக்காட்டாக, பதிப்பு `` 1.1.post1`` கொடுக்கப்பட்டால், பின்வரும் உட்பிரிவுகள் " "பொருந்தாது அல்லது காட்டப்பட்டுள்ளபடி இல்லை ::" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " @@ -31020,7 +31006,7 @@ msgstr "" "முன்னொட்டு பொருத்தத்தின் நோக்கங்களுக்காக, வெளியீட்டுக்கு முந்தைய பிரிவு `` .`` க்கு " "முந்தைய ஒரு மறைமுகத்தைக் கொண்டிருப்பதாகக் கருதப்படுகிறது, எனவே பதிப்பு `` 1.1a1```" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -31032,7 +31018,7 @@ msgstr "" "குறிக்கப்படுகிறது). பதிப்பு `` 1.1`` கொடுக்கப்பட்டால், பின்வரும் உட்பிரிவுகள் பொருந்தாது " "அல்லது காட்டப்பட்டுள்ளபடி இல்லை ::" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -31046,7 +31032,7 @@ msgstr "" "நோக்கங்களுக்காக புறக்கணிக்கப்படுகிறது, எனவே முன்னொட்டு போட்டியில் பயன்படுத்துவது எந்த " "அர்த்தமும் இல்லை." -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -31062,7 +31048,7 @@ msgstr "" "சார்புகளை வரையறுக்கும் போது கடுமையான பதிப்பு ஒப்பீட்டு ஆபரேட்டர் முதன்மையாக " "பயன்பாட்டிற்காக கருதப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " @@ -31072,7 +31058,7 @@ msgstr "" "சிட்டை இல்லை) என்றால், எந்த வேட்பாளர் பதிப்புகளின் உள்ளக பதிப்பு சிட்டை பதிப்புகளுடன் " "பொருந்தும்போது புறக்கணிக்கப்பட வேண்டும்." -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -31086,11 +31072,11 @@ msgstr "" "உள்ளக பதிப்பு சிட்டை ஒரு கடுமையான சரம் சமத்துவ ஒப்பீட்டைப் பயன்படுத்தி சமநிலைக்கு " "சரிபார்க்கப்படுகிறது." -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "பதிப்பு விலக்கு" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." @@ -31098,7 +31084,7 @@ msgstr "" "பதிப்பு விலக்கு பிரிவில் பதிப்பு விலக்கு ஆபரேட்டர் ``! = `` மற்றும் பதிப்பு " "அடையாளங்காட்டி ஆகியவை அடங்கும்." -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " @@ -31107,11 +31093,11 @@ msgstr "" "அனுமதிக்கப்பட்ட பதிப்பு அடையாளங்காட்டிகள் மற்றும் ஒப்பீட்டு சொற்பொருள்கள் `பதிப்பு " "பொருத்துதல்`_ ஆபரேட்டருக்கு சமமானவை, தவிர எந்தவொரு போட்டியின் உணர்வும் தலைகீழாக உள்ளது." -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "உள்ளடக்கிய உத்தரவிட்ட ஒப்பீடு" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -31124,12 +31110,12 @@ msgstr "" "`பதிப்பு திட்டம்`_ ஆல் வரையறுக்கப்பட்ட நிலையான வரிசைப்படுத்தல் கொடுக்கப்பட்ட குறிப்பிட்ட " "பதிப்பின் அடிப்படையில் ஒப்பீடு சரியானதாக இருக்கும் எந்த பதிப்பையும் பொருத்துகிறது." -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "உள்ளடக்கிய உத்தரவிடப்பட்ட ஒப்பீட்டு ஆபரேட்டர்கள் `` <= `` மற்றும் ``> = ``." -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." @@ -31137,16 +31123,16 @@ msgstr "" "பதிப்பு பொருத்தத்தைப் போலவே, வெளியீட்டு பிரிவுகள் ஒரே நீளத்துடன் ஒப்பிடப்படுவதை " "உறுதிசெய்ய தேவையான அளவு பூச்சியத் துடுப்பு ஆகும்." -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "இந்த பதிப்பு விவரக்குறிப்பில் உள்ளக பதிப்பு அடையாளங்காட்டிகள் அனுமதிக்கப்படவில்லை." -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "பிரத்தியேக உத்தரவிடப்பட்ட ஒப்பீடு" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -31161,7 +31147,7 @@ msgstr "" "கொடுக்கப்பட்ட குறிப்பிட்ட பதிப்பாகும். இருப்பினும், அவை குறிப்பிட்ட பதிப்பின் முன் " "வெளியீடுகள், பிந்தைய வெளியீடுகள் மற்றும் உள்ளக பதிப்புகளை குறிப்பாக விலக்குகின்றன." -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -31177,7 +31163,7 @@ msgstr "" "`` 1.7.0.post1`` மற்றும் `> 1.7.post2`` ஐ அனுமதிக்கும்` `1.7.1``` மற்றும்` `1.7.0." "post3`` அல்ல, ஆனால்` `1.7.0``." -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." @@ -31185,7 +31171,7 @@ msgstr "" "பிரத்யேக ஆர்டர் செய்யப்பட்ட ஒப்பீடு ``> v`` ** குறிப்பிட்ட பதிப்பின் உள்ளக பதிப்போடு " "பொருந்தக்கூடாது." -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " @@ -31470,7 +31456,7 @@ msgstr "" "`` முகவரி துண்டின் ஒரு பகுதியாக நுழைவு ஆகியவற்றைச் சேர்ப்பதன் மூலம் எதிர்பார்க்கப்படும் " "ஆச் மதிப்பு குறிப்பிடப்படலாம்." -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -31485,7 +31471,7 @@ msgstr "" "பதிப்பு கட்டுப்பாட்டு அமைப்புகளுக்கான ஆச்களைக் காணவில்லை என்ற எச்சரிக்கைகளை தானியங்கு " "கருவிகள் தவிர்க்கலாம்." -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -31496,7 +31482,7 @@ msgstr "" "அமைப்புகளைக் கையாள, அந்த செய்தி `` `<கமிட்-ஆச்>` அல்லது ``@<குறிச்சொல்>#<கமிட்-ஆச்> `` " "குறியீட்டைப் பயன்படுத்தி முகவரி இன் முடிவில் சேர்க்கப்படலாம்." -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -31514,15 +31500,15 @@ msgstr "" "குறிச்சொல்லுடன் தீங்கிழைக்கும் ரெப்போவை உருவாக்குவது எளிதானது, ஒரு குறிப்பிட்ட *ஆச் *உடன் " "ஒன்றை உருவாக்குகிறது, குறைவாக)." -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "தொலைநிலை முகவரி எடுத்துக்காட்டுகள் ::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "கோப்பு முகவரி கள்" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -31534,7 +31520,7 @@ msgstr "" "தவிர்க்கப்பட்டாலும் கூட மூன்றாவது சாய்வு இன்னும் இருக்க வேண்டும். `` `` `அணுக " "வேண்டிய கோப்பு முறைமையின் கோப்பு பாதை என்ன என்பதை வரையறுக்கிறது." -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -31546,7 +31532,7 @@ msgstr "" "அதன் சொந்த ஓச்டுடன் பொருந்துகிறது. வேறு வார்த்தைகளில் கூறுவதானால், `` கோப்பு: // `` " "திட்டத்தை உள்ளக கணினியில் பாதைகளை அணுக மட்டுமே பயன்படுத்த முடியும்." -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -31565,11 +31551,11 @@ msgstr "" "தொகுதி/கோப்பு`` என முடிவடையும். சாளரங்களில் `` கோப்பு: // `` urls பற்றிய கூடுதல் " "தகவலுக்கு `msdtn _ _ திட்டம்):" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "ஆகச்ட் 2014: இந்த விவரக்குறிப்பு அங்கீகரிக்கப்பட்டது: PEP: `440`." +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "பைதான் மெய்நிகர் சூழல்கள்" @@ -33844,6 +33836,63 @@ msgstr "" "மட்டுமே தொடங்கினால், * வழக்கமான தொகுப்புகள் * மற்றும் `__init __. பை`` (கோப்பு " "காலியாக இருந்தாலும் கூட) ஒட்டிக்கொள்ள பரிந்துரைக்கப்படுகிறது." +#~ msgid "Signing the distribution packages" +#~ msgstr "விநியோக தொகுப்புகளில் கையொப்பமிடுதல்" + +#~ msgid "" +#~ "The following job signs the distribution packages with `Sigstore`_, the " +#~ "same artifact signing system `used to sign CPython `_." +#~ msgstr "" +#~ "பின்வரும் வேலை விநியோக தொகுப்புகளை `சிக்ச்டோர்`_ உடன் கையொப்பமிடுகிறது, அதே " +#~ "கலைப்பொருள் கையொப்பமிடும் அமைப்பு` cpython `_ இல் கையொப்பமிடப் பயன்படுகிறது." + +#~ msgid "" +#~ "Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ " +#~ "to sign the distribution packages. In the next step, an empty GitHub " +#~ "Release from the current tag is created using the ``gh`` CLI. Note this " +#~ "step can be further customised. See the `gh release documentation " +#~ "`_ as a reference." +#~ msgstr "" +#~ "முதலாவதாக, விநியோக தொகுப்புகளில் கையெழுத்திட இது `சிக்ச்டோர்/சிஎச்-ஆக்சன்-சிக்ச்டோர்-" +#~ "பைதான் அறிவிலிமையம் அதிரடி`_ ஐப் பயன்படுத்துகிறது. அடுத்த கட்டத்தில், தற்போதைய " +#~ "குறிச்சொல்லிலிருந்து வெற்று அறிவிலிமையம் வெளியீடு `` gh`` Cli ஐப் பயன்படுத்தி " +#~ "உருவாக்கப்படுகிறது. இந்த படி மேலும் தனிப்பயனாக்கப்படலாம் என்பதை நினைவில் கொள்க. " +#~ "`சிஎச் வெளியீட்டு ஆவணங்கள் _ _ ஒரு " +#~ "குறிப்பாகப் பார்க்கவும்." + +#~ msgid "" +#~ "You may need to manage your ``GITHUB_TOKEN`` permissions to enable " +#~ "creating the GitHub Release. See the `GitHub documentation `_ for " +#~ "instructions. Specifically, the token needs the ``contents: write`` " +#~ "permission." +#~ msgstr "" +#~ "அறிவிலிமையம் வெளியீட்டை உருவாக்க உங்கள் `` github_token`` அனுமதிகளை நிர்வகிக்க " +#~ "வேண்டியிருக்கலாம். `கிட்அப் ஆவணங்கள் `_ அறிவுறுத்தல்களுக்கு. குறிப்பாக, " +#~ "டோக்கனுக்கு `` உள்ளடக்கங்கள்: எழுது `அனுமதி தேவை." + +#~ msgid "" +#~ "Finally, the signed distributions are uploaded to the GitHub Release." +#~ msgstr "" +#~ "இறுதியாக, கையொப்பமிடப்பட்ட விநியோகங்கள் அறிவிலிமையம் வெளியீட்டில் பதிவேற்றப்படுகின்றன." + +#~ msgid "" +#~ "This is a replacement for GPG signatures, for which support has been " +#~ "`removed from PyPI `_. However, this job is not mandatory for uploading to PyPI and can be " +#~ "omitted." +#~ msgstr "" +#~ "இது சிபிசி கையொப்பங்களுக்கு மாற்றாக உள்ளது, இதற்காக பைபி `_ இலிருந்து உதவி அகற்றப்பட்டுள்ளது. " +#~ "இருப்பினும், இந்த வேலை PYPI இல் பதிவேற்றுவதற்கு கட்டாயமில்லை, மேலும் தவிர்க்கப்படலாம்." + #~ msgid "" #~ "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 \n" "Language-Team: Turkish `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8558,7 +8558,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8583,79 +8583,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8663,7 +8629,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8672,7 +8638,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13574,7 +13540,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23025,7 +22991,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23497,7 +23463,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23507,28 +23479,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23539,18 +23511,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23558,22 +23530,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23582,11 +23554,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23596,11 +23568,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23610,11 +23582,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23622,11 +23594,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23637,11 +23609,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23649,11 +23621,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23661,11 +23633,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23675,11 +23647,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23687,11 +23659,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23699,11 +23671,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23711,11 +23683,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23724,11 +23696,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23737,11 +23709,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23751,7 +23723,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23759,69 +23731,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23829,48 +23801,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23881,7 +23853,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23891,17 +23863,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23910,14 +23882,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23928,7 +23900,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23936,30 +23908,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23967,30 +23939,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -23998,60 +23970,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24060,79 +24032,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24141,7 +24113,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24149,7 +24121,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24159,21 +24131,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24181,7 +24153,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24190,7 +24162,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24200,14 +24172,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24216,28 +24188,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24246,27 +24218,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24276,7 +24248,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24286,13 +24258,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24512,7 +24484,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24520,7 +24492,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24531,15 +24503,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24547,7 +24519,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24555,7 +24527,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24567,43 +24539,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24612,23 +24584,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/uk/LC_MESSAGES/messages.po b/locales/uk/LC_MESSAGES/messages.po index 1c9959643..2f9f035ac 100644 --- a/locales/uk/LC_MESSAGES/messages.po +++ b/locales/uk/LC_MESSAGES/messages.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-03-01 20:00+0000\n" "Last-Translator: Sviatoslav Sydorenko \n" "Language-Team: Ukrainian `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -9048,7 +9048,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -9073,81 +9073,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -#, fuzzy -#| msgid "Distribution Package" -msgid "Signing the distribution packages" -msgstr "Дистриб'юторський пакет" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "Це все, добродії!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9155,7 +9119,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9164,7 +9128,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -14128,7 +14092,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23745,7 +23709,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -24226,7 +24190,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -24236,29 +24206,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -24269,19 +24239,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 #, fuzzy msgid "Normalization" msgstr "Переклади" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -24289,23 +24259,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "Переклади" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -24314,13 +24284,13 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 #, fuzzy #| msgid "Pre-release versioning" msgid "Pre-release separators" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -24330,13 +24300,13 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 #, fuzzy #| msgid "Pre-release versioning" msgid "Pre-release spelling" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -24346,11 +24316,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24358,11 +24328,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -24373,13 +24343,13 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 #, fuzzy #| msgid "Pre-release versioning" msgid "Post release spelling" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -24387,11 +24357,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24399,11 +24369,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -24413,11 +24383,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24425,11 +24395,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -24437,13 +24407,13 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 #, fuzzy #| msgid "Local version identifiers" msgid "Local version segments" msgstr "Ідентифікатори місцевих версій" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -24451,11 +24421,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -24464,11 +24434,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24477,13 +24447,13 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 #, fuzzy #| msgid "Here are some examples of compliant version numbers::" msgid "Examples of compliant version schemes" msgstr "Ось кілька прикладів сумісних номерів версій::" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24493,7 +24463,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24501,71 +24471,71 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 #, fuzzy #| msgid "Serial versioning" msgid "Simple \"major.minor\" versioning::" msgstr "Порядкове версіонування" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24573,48 +24543,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24625,7 +24595,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24635,17 +24605,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24654,14 +24624,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24672,7 +24642,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24680,32 +24650,32 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 #, fuzzy #| msgid "Date based versioning" msgid "DVCS based version labels" msgstr "Версіонування базоване на датах" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24713,32 +24683,32 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 #, fuzzy #| msgid "Date based versioning" msgid "Olson database versioning" msgstr "Версіонування базоване на датах" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24746,60 +24716,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24808,81 +24778,81 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 #, fuzzy #| msgid "Version" msgid "Version matching" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24891,7 +24861,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24899,7 +24869,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24909,21 +24879,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24931,7 +24901,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24940,7 +24910,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24950,14 +24920,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24966,30 +24936,30 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy #| msgid "Version Specifier" msgid "Version exclusion" msgstr "Специфікатор версії" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24998,27 +24968,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -25028,7 +24998,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -25038,13 +25008,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -25264,7 +25234,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -25272,7 +25242,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -25283,17 +25253,17 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 #, fuzzy #| msgid "For example::" msgid "Remote URL examples::" msgstr "Наприклад::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -25301,7 +25271,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -25309,7 +25279,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -25321,43 +25291,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -25366,23 +25336,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" @@ -27075,6 +27051,11 @@ msgid "" "the file is empty)." msgstr "" +#, fuzzy +#~| msgid "Distribution Package" +#~ msgid "Signing the distribution packages" +#~ msgstr "Дистриб'юторський пакет" + #, fuzzy #~| msgid "Additional tools" #~ msgid "Additional file information" diff --git a/locales/vi/LC_MESSAGES/messages.po b/locales/vi/LC_MESSAGES/messages.po index f7c206e93..ed97763bd 100644 --- a/locales/vi/LC_MESSAGES/messages.po +++ b/locales/vi/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2024-07-25 13:10+0000\n" "Last-Translator: Lenny Tran \n" "Language-Team: Vietnamese `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8583,7 +8583,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8608,79 +8608,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8688,7 +8654,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8697,7 +8663,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13599,7 +13565,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -23054,7 +23020,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23526,7 +23492,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23536,28 +23508,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23568,18 +23540,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23587,22 +23559,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23611,11 +23583,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23625,11 +23597,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23639,11 +23611,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23651,11 +23623,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23666,11 +23638,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23678,11 +23650,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23690,11 +23662,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23704,11 +23676,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23716,11 +23688,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23728,11 +23700,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23740,11 +23712,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23753,11 +23725,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23766,11 +23738,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23780,7 +23752,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23788,69 +23760,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -23858,48 +23830,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -23910,7 +23882,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -23920,17 +23892,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -23939,14 +23911,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -23957,7 +23929,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -23965,30 +23937,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -23996,30 +23968,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24027,60 +23999,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24089,79 +24061,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24170,7 +24142,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24178,7 +24150,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24188,21 +24160,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24210,7 +24182,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24219,7 +24191,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24229,14 +24201,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24245,28 +24217,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24275,27 +24247,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24305,7 +24277,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24315,13 +24287,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24541,7 +24513,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24549,7 +24521,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24560,15 +24532,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24576,7 +24548,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24584,7 +24556,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24596,43 +24568,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24641,23 +24613,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "" diff --git a/locales/zh_Hans/LC_MESSAGES/messages.po b/locales/zh_Hans/LC_MESSAGES/messages.po index f6ef33f92..de6a28e52 100644 --- a/locales/zh_Hans/LC_MESSAGES/messages.po +++ b/locales/zh_Hans/LC_MESSAGES/messages.po @@ -35,10 +35,10 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" -"PO-Revision-Date: 2025-04-27 04:57+0000\n" -"Last-Translator: 大王叫我来巡山 \n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" +"PO-Revision-Date: 2025-05-15 01:03+0000\n" +"Last-Translator: 大王叫我来巡山 " +"\n" "Language-Team: Chinese (Simplified Han script) \n" "Language: zh_Hans\n" @@ -3155,7 +3155,7 @@ msgstr "" "通常以补丁版本发布，但不可避免地包含破坏性更改。" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:726 msgid "Semantic versioning" msgstr "语义版本控制" @@ -4522,7 +4522,7 @@ msgstr "描述" #: ../source/specifications/dependency-groups.rst:23 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:357 -#: ../source/specifications/version-specifiers.rst:1069 +#: ../source/specifications/version-specifiers.rst:1072 msgid "Examples" msgstr "例子" @@ -9175,12 +9175,12 @@ msgid "" msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:25 -msgid "Configuring trusted publishing" -msgstr "" +msgid "Configuring Trusted Publishing" +msgstr "配置可信发布" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:27 msgid "" -"This guide relies on PyPI's `trusted publishing`_ implementation to connect " +"This guide relies on PyPI's `Trusted Publishing`_ implementation to connect " "to `GitHub Actions CI/CD`_. This is recommended for security reasons, since " "the generated tokens are created for each of your projects individually and " "expire automatically. Otherwise, you'll need to generate an `API token`_ for " @@ -9194,7 +9194,7 @@ msgid "" "Since this guide will demonstrate uploading to both PyPI and TestPyPI, we'll " "need two trusted publishers configured. The following steps will lead you " "through creating the \"pending\" publishers for your new :term:`PyPI project " -"`. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -9317,7 +9317,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -9342,79 +9342,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "签署分发包" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 -msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "就这些了，伙计们!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9422,7 +9388,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9431,7 +9397,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -14485,7 +14451,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -16710,7 +16676,7 @@ msgstr "Python 同等项" #: ../source/specifications/dependency-specifiers.rst:249 msgid "Type" -msgstr "" +msgstr "类型" #: ../source/specifications/dependency-specifiers.rst:250 msgid "Sample values" @@ -16832,10 +16798,8 @@ msgstr "" #: ../source/specifications/dependency-specifiers.rst:284 #: ../source/specifications/dependency-specifiers.rst:288 #: ../source/specifications/dependency-specifiers.rst:296 -#, fuzzy -#| msgid "Version Specifier" msgid ":ref:`Version `" -msgstr "版本说明符 (Version Specifier)" +msgstr ":ref:`Version `" #: ../source/specifications/dependency-specifiers.rst:285 msgid "``3.4``, ``2.7``" @@ -16886,17 +16850,13 @@ msgid "" msgstr "" #: ../source/specifications/dependency-specifiers.rst:302 -#, fuzzy -#| msgid "``pyproject.toml``" msgid "``toml``" -msgstr "``pyproject.toml``" +msgstr "``toml``" #: ../source/specifications/dependency-specifiers.rst:303 #: ../source/specifications/pylock-toml.rst:108 -#, fuzzy -#| msgid "``alias``" msgid "``extras``" -msgstr "``alias``" +msgstr "``extras``" #: ../source/specifications/dependency-specifiers.rst:306 #: ../source/specifications/dependency-specifiers.rst:311 @@ -16908,10 +16868,8 @@ msgid "``{\"toml\"}``" msgstr "" #: ../source/specifications/dependency-specifiers.rst:308 -#, fuzzy -#| msgid "``dependencies``" msgid "``dependency_groups``" -msgstr "``dependencies``" +msgstr "``dependency_groups``" #: ../source/specifications/dependency-specifiers.rst:312 msgid "``{\"test\"}``" @@ -19813,10 +19771,8 @@ msgid "March 2024: The tags for Android were approved through :pep:`738`." msgstr "" #: ../source/specifications/pylock-toml.rst:6 -#, fuzzy -#| msgid "``pyproject.toml`` specification" msgid "``pylock.toml`` Specification" -msgstr "``pyproject.toml`` 规格" +msgstr "``pylock.toml`` 规范" #: ../source/specifications/pylock-toml.rst:8 msgid "" @@ -19829,10 +19785,8 @@ msgid "This specification was originally defined in :pep:`751`." msgstr "" #: ../source/specifications/pylock-toml.rst:16 -#, fuzzy -#| msgid "Name" msgid "File Name" -msgstr "名称" +msgstr "文件名称" #: ../source/specifications/pylock-toml.rst:18 msgid "" @@ -19897,10 +19851,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:65 -#, fuzzy -#| msgid "``python_version``" msgid "``lock-version``" -msgstr "``python_version``" +msgstr "``lock-version``" #: ../source/specifications/pylock-toml.rst:67 msgid "**Type**: string; value of ``\"1.0\"``" @@ -19915,10 +19867,8 @@ msgstr "" #: ../source/specifications/pylock-toml.rst:397 #: ../source/specifications/pylock-toml.rst:494 #: ../source/specifications/pylock-toml.rst:689 -#, fuzzy -#| msgid "Requires" msgid "**Required?**: yes" -msgstr "要求" +msgstr "**必需吗？**: 是" #: ../source/specifications/pylock-toml.rst:69 msgid "**Inspiration**: :ref:`core-metadata-metadata-version`" @@ -19945,10 +19895,8 @@ msgid "If a tool doesn't support a major version, it MUST raise an error." msgstr "" #: ../source/specifications/pylock-toml.rst:81 -#, fuzzy -#| msgid "``entry-points``" msgid "``environments``" -msgstr "``entry-points``" +msgstr "``environments``" #: ../source/specifications/pylock-toml.rst:83 #: ../source/specifications/pylock-toml.rst:110 @@ -20067,17 +20015,13 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:130 -#, fuzzy -#| msgid "``dependencies``" msgid "``dependency-groups``" -msgstr "``dependencies``" +msgstr "``dependency-groups``" #: ../source/specifications/pylock-toml.rst:134 #: ../source/specifications/pylock-toml.rst:716 -#, fuzzy -#| msgid ":ref:`pyproject-toml-spec`" msgid "**Inspiration**: :ref:`pyproject-tool-table`" -msgstr ":ref:`pyproject-toml-spec`" +msgstr "**灵感**: :ref:`pyproject-tool-table`" #: ../source/specifications/pylock-toml.rst:135 msgid "" @@ -20152,10 +20096,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:186 -#, fuzzy -#| msgid "``packages``" msgid "``[[packages]]``" -msgstr "``packages``" +msgstr "``[[packages]]``" #: ../source/specifications/pylock-toml.rst:188 #: ../source/specifications/pylock-toml.rst:254 @@ -20175,10 +20117,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:199 -#, fuzzy -#| msgid "``packages``" msgid "``packages.name``" -msgstr "``packages``" +msgstr "``packages.name``" #: ../source/specifications/pylock-toml.rst:203 msgid "**Inspiration**: :ref:`core-metadata-name`" @@ -20189,20 +20129,16 @@ msgid "The name of the package :ref:`normalized `." msgstr "" #: ../source/specifications/pylock-toml.rst:210 -#, fuzzy -#| msgid "``packages``" msgid "``packages.version``" -msgstr "``packages``" +msgstr "``packages.version``" #: ../source/specifications/pylock-toml.rst:214 msgid "**Inspiration**: :ref:`core-metadata-version`" msgstr "" #: ../source/specifications/pylock-toml.rst:215 -#, fuzzy -#| msgid "Creating the package" msgid "The version of the package." -msgstr "创建包" +msgstr "包版本。" #: ../source/specifications/pylock-toml.rst:216 msgid "" @@ -20219,10 +20155,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:227 -#, fuzzy -#| msgid "``packages``" msgid "``packages.marker``" -msgstr "``packages``" +msgstr "``packages.marker``" #: ../source/specifications/pylock-toml.rst:231 msgid "**Inspiration**: PDM_" @@ -20235,10 +20169,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:240 -#, fuzzy -#| msgid "``packages``" msgid "``packages.requires-python``" -msgstr "``packages``" +msgstr "``packages.requires-python``" #: ../source/specifications/pylock-toml.rst:244 msgid "**Inspiration**: :ref:`core-metadata-requires-python`" @@ -20251,10 +20183,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:252 -#, fuzzy -#| msgid "``dependencies``" msgid "``[[packages.dependencies]]``" -msgstr "``dependencies``" +msgstr "``[[packages.dependencies]]``" #: ../source/specifications/pylock-toml.rst:257 msgid "" @@ -20279,10 +20209,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:272 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.vcs]``" -msgstr "``packages``" +msgstr "``[packages.vcs]``" #: ../source/specifications/pylock-toml.rst:274 #: ../source/specifications/pylock-toml.rst:376 @@ -20333,10 +20261,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:294 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.type``" -msgstr "``packages``" +msgstr "``packages.vcs.type``" #: ../source/specifications/pylock-toml.rst:296 msgid "" @@ -20353,16 +20279,12 @@ msgid "**Inspiration**: :ref:`direct-url-data-structure-vcs`" msgstr "" #: ../source/specifications/pylock-toml.rst:300 -#, fuzzy -#| msgid "Install from version control systems" msgid "The type of version control system used." -msgstr "从版本控制系统进行安装" +msgstr "所用的版本控制系统类型。" #: ../source/specifications/pylock-toml.rst:306 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.url``" -msgstr "``packages``" +msgstr "``packages.vcs.url``" #: ../source/specifications/pylock-toml.rst:309 msgid "**Required?**: if :ref:`pylock-packages-vcs-path` is not specified" @@ -20373,10 +20295,8 @@ msgid "The URL_ to the source tree." msgstr "" #: ../source/specifications/pylock-toml.rst:317 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.path``" -msgstr "``packages``" +msgstr "``packages.vcs.path``" #: ../source/specifications/pylock-toml.rst:320 msgid "**Required?**: if :ref:`pylock-packages-vcs-url` is not specified" @@ -20412,10 +20332,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:345 -#, fuzzy -#| msgid "``packages``" msgid "``packages.vcs.commit-id``" -msgstr "``packages``" +msgstr "``packages.vcs.commit-id``" #: ../source/specifications/pylock-toml.rst:350 msgid "The exact commit/revision number that is to be installed." @@ -20448,10 +20366,8 @@ msgid "The path MUST be relative to the root of the source tree structure." msgstr "" #: ../source/specifications/pylock-toml.rst:374 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.directory]``" -msgstr "``packages``" +msgstr "``[packages.directory]``" #: ../source/specifications/pylock-toml.rst:377 msgid "" @@ -20491,10 +20407,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:394 -#, fuzzy -#| msgid "``package_data``" msgid "``packages.directory.path``" -msgstr "``package_data``" +msgstr "``packages.directory.path``" #: ../source/specifications/pylock-toml.rst:399 msgid "The local directory where the source tree is." @@ -20547,10 +20461,8 @@ msgid "See :ref:`pylock-packages-vcs-subdirectory`." msgstr "" #: ../source/specifications/pylock-toml.rst:432 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.archive]``" -msgstr "``packages``" +msgstr "``[packages.archive]``" #: ../source/specifications/pylock-toml.rst:436 msgid "**Inspiration**: :ref:`direct-url-data-structure-archive`" @@ -20581,30 +20493,24 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:450 -#, fuzzy -#| msgid "``packages``" msgid "``packages.archive.url``" -msgstr "``packages``" +msgstr "``packages.archive.url``" #: ../source/specifications/pylock-toml.rst:452 msgid "See :ref:`pylock-packages-vcs-url`." msgstr "" #: ../source/specifications/pylock-toml.rst:458 -#, fuzzy -#| msgid "``packages``" msgid "``packages.archive.path``" -msgstr "``packages``" +msgstr "``packages.archive.path``" #: ../source/specifications/pylock-toml.rst:460 msgid "See :ref:`pylock-packages-vcs-path`." msgstr "" #: ../source/specifications/pylock-toml.rst:466 -#, fuzzy -#| msgid "``packages``" msgid "``packages.archive.size``" -msgstr "``packages``" +msgstr "``packages.archive.size``" #: ../source/specifications/pylock-toml.rst:468 msgid "**Type**: integer" @@ -20637,10 +20543,8 @@ msgid "**Inspiration**: :ref:`simple-repository-api`" msgstr "" #: ../source/specifications/pylock-toml.rst:484 -#, fuzzy -#| msgid "Where the guide is deployed" msgid "The time the file was uploaded." -msgstr "指南的部署地点" +msgstr "文件上传时间。" #: ../source/specifications/pylock-toml.rst:485 msgid "The date and time MUST be recorded in UTC." @@ -20684,10 +20588,8 @@ msgid "``packages.archive.subdirectory``" msgstr "" #: ../source/specifications/pylock-toml.rst:516 -#, fuzzy -#| msgid "``packages``" msgid "``packages.index``" -msgstr "``packages``" +msgstr "``packages.index``" #: ../source/specifications/pylock-toml.rst:521 msgid "" @@ -20709,10 +20611,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:533 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.sdist]``" -msgstr "``packages``" +msgstr "``[packages.sdist]``" #: ../source/specifications/pylock-toml.rst:536 #: ../source/specifications/pylock-toml.rst:606 @@ -20737,10 +20637,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:549 -#, fuzzy -#| msgid "``package_data``" msgid "``packages.sdist.name``" -msgstr "``package_data``" +msgstr "``packages.sdist.name``" #: ../source/specifications/pylock-toml.rst:552 msgid "" @@ -20753,10 +20651,8 @@ msgid "The file name of the :ref:`source-distribution-format-sdist` file." msgstr "" #: ../source/specifications/pylock-toml.rst:562 -#, fuzzy -#| msgid "``package_data``" msgid "``packages.sdist.upload-time``" -msgstr "``package_data``" +msgstr "``packages.sdist.upload-time``" #: ../source/specifications/pylock-toml.rst:564 #: ../source/specifications/pylock-toml.rst:633 @@ -20764,10 +20660,8 @@ msgid "See :ref:`pylock-packages-archive-upload-time`." msgstr "" #: ../source/specifications/pylock-toml.rst:570 -#, fuzzy -#| msgid "``packages``" msgid "``packages.sdist.url``" -msgstr "``packages``" +msgstr "``packages.sdist.url``" #: ../source/specifications/pylock-toml.rst:572 #: ../source/specifications/pylock-toml.rst:641 @@ -20775,10 +20669,8 @@ msgid "See :ref:`pylock-packages-archive-url`." msgstr "" #: ../source/specifications/pylock-toml.rst:578 -#, fuzzy -#| msgid "``package_data``" msgid "``packages.sdist.path``" -msgstr "``package_data``" +msgstr "``packages.sdist.path``" #: ../source/specifications/pylock-toml.rst:580 #: ../source/specifications/pylock-toml.rst:649 @@ -20786,10 +20678,8 @@ msgid "See :ref:`pylock-packages-archive-path`." msgstr "" #: ../source/specifications/pylock-toml.rst:586 -#, fuzzy -#| msgid "``packages``" msgid "``packages.sdist.size``" -msgstr "``packages``" +msgstr "``packages.sdist.size``" #: ../source/specifications/pylock-toml.rst:588 #: ../source/specifications/pylock-toml.rst:657 @@ -20797,10 +20687,8 @@ msgid "See :ref:`pylock-packages-archive-size`." msgstr "" #: ../source/specifications/pylock-toml.rst:594 -#, fuzzy -#| msgid "``package_data``" msgid "``packages.sdist.hashes``" -msgstr "``package_data``" +msgstr "``packages.sdist.hashes``" #: ../source/specifications/pylock-toml.rst:596 #: ../source/specifications/pylock-toml.rst:665 @@ -20808,10 +20696,8 @@ msgid "See :ref:`pylock-packages-archive-hashes`." msgstr "" #: ../source/specifications/pylock-toml.rst:603 -#, fuzzy -#| msgid "``packages``" msgid "``[[packages.wheels]]``" -msgstr "``packages``" +msgstr "``[[packages.wheels]]``" #: ../source/specifications/pylock-toml.rst:609 msgid "" @@ -20826,10 +20712,8 @@ msgid "" msgstr "" #: ../source/specifications/pylock-toml.rst:618 -#, fuzzy -#| msgid "``packages``" msgid "``packages.wheels.name``" -msgstr "``packages``" +msgstr "``packages.wheels.name``" #: ../source/specifications/pylock-toml.rst:621 msgid "" @@ -20846,28 +20730,20 @@ msgid "``packages.wheels.upload-time``" msgstr "" #: ../source/specifications/pylock-toml.rst:639 -#, fuzzy -#| msgid "``packages``" msgid "``packages.wheels.url``" -msgstr "``packages``" +msgstr "``packages.wheels.url``" #: ../source/specifications/pylock-toml.rst:647 -#, fuzzy -#| msgid "``packages``" msgid "``packages.wheels.path``" -msgstr "``packages``" +msgstr "``packages.wheels.path``" #: ../source/specifications/pylock-toml.rst:655 -#, fuzzy -#| msgid "``packages``" msgid "``packages.wheels.size``" -msgstr "``packages``" +msgstr "``packages.wheels.size``" #: ../source/specifications/pylock-toml.rst:663 -#, fuzzy -#| msgid "``packages``" msgid "``packages.wheels.hashes``" -msgstr "``packages``" +msgstr "``packages.wheels.hashes``" #: ../source/specifications/pylock-toml.rst:671 msgid "``[[packages.attestation-identities]]``" @@ -20902,16 +20778,12 @@ msgid "The unique identity of the Trusted Publisher." msgstr "" #: ../source/specifications/pylock-toml.rst:697 -#, fuzzy -#| msgid "``packages``" msgid "``[packages.tool]``" -msgstr "``packages``" +msgstr "``[packages.tool]``" #: ../source/specifications/pylock-toml.rst:701 -#, fuzzy -#| msgid ":ref:`pyproject-toml-spec`" msgid "**Inspiration**: :ref:` pyproject-tool-table`" -msgstr ":ref:`pyproject-toml-spec`" +msgstr "**灵感**: :ref:` pyproject-tool-table`" #: ../source/specifications/pylock-toml.rst:702 msgid "" @@ -22327,10 +22199,8 @@ msgid "Python Description Formats" msgstr "Python 描述格式" #: ../source/specifications/section-reproducible-environments.rst:3 -#, fuzzy -#| msgid "Virtual Environment" msgid "Reproducible Environments" -msgstr "虚拟环境 (Virtual Environment)" +msgstr "可重复的环境" #: ../source/specifications/simple-repository-api.rst:6 msgid "Simple repository API" @@ -24038,7 +23908,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -24510,7 +24380,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -24520,28 +24396,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 msgid "Version epochs" msgstr "重要版本" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -24552,18 +24428,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "规范化" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -24571,22 +24447,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 msgid "Integer Normalization" msgstr "整数规范化" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -24595,11 +24471,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -24609,11 +24485,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -24623,11 +24499,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24635,11 +24511,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -24650,11 +24526,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -24662,11 +24538,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -24674,11 +24550,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -24688,11 +24564,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24700,11 +24576,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -24712,11 +24588,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "本地版本部分" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -24724,11 +24600,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -24737,11 +24613,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24750,11 +24626,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24764,7 +24640,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24772,69 +24648,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24842,48 +24718,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24894,7 +24770,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24904,17 +24780,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24923,14 +24799,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24941,7 +24817,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24949,30 +24825,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24980,30 +24856,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -25011,60 +24887,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -25073,79 +24949,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "版本匹配" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -25154,7 +25030,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -25162,7 +25038,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -25172,21 +25048,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -25194,7 +25070,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -25203,7 +25079,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -25213,14 +25089,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -25229,28 +25105,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 msgid "Version exclusion" msgstr "版本排除" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -25259,27 +25135,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -25289,7 +25165,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -25299,13 +25175,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -25527,7 +25403,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -25535,7 +25411,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -25546,15 +25422,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "远程 URL 示例::" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -25562,7 +25438,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -25570,7 +25446,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -25582,43 +25458,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -25627,23 +25503,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr "Python 虚拟环境" @@ -27306,6 +27188,9 @@ msgid "" "the file is empty)." msgstr "" +#~ msgid "Signing the distribution packages" +#~ msgstr "签署分发包" + #~ msgid "Additional file information" #~ msgstr "附加的文件信息" diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po index 221cc5fc3..a4b5fa78d 100644 --- a/locales/zh_Hant/LC_MESSAGES/messages.po +++ b/locales/zh_Hant/LC_MESSAGES/messages.po @@ -14,7 +14,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-05-02 23:58+0000\n" +"POT-Creation-Date: 2025-05-13 20:48+0000\n" "PO-Revision-Date: 2025-02-24 15:37+0000\n" "Last-Translator: toto6038 \n" "Language-Team: Chinese (Traditional Han script) `. However it is also possible to add `trusted publishing`_ to any " +"`. However it is also possible to add `Trusted Publishing`_ to any " "pre-existing project, if you are its owner." msgstr "" @@ -8655,7 +8655,7 @@ msgid "" "This also defines a GitHub Environment for the job to run in its context and " "a URL to be displayed in GitHub's UI nicely. Additionally, it allows " "acquiring an OpenID Connect token that the ``pypi-publish`` actions needs to " -"implement secretless trusted publishing to PyPI." +"implement secretless Trusted Publishing to PyPI." msgstr "" #: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:144 @@ -8680,79 +8680,45 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 -msgid "Signing the distribution packages" -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:165 -msgid "" -"The following job signs the distribution packages with `Sigstore`_, the same " -"artifact signing system `used to sign CPython `_." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:168 -msgid "" -"Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_ to " -"sign the distribution packages. In the next step, an empty GitHub Release " -"from the current tag is created using the ``gh`` CLI. Note this step can be " -"further customised. See the `gh release documentation `_ as a reference." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:176 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 msgid "" -"You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating " -"the GitHub Release. See the `GitHub documentation `_ for " -"instructions. Specifically, the token needs the ``contents: write`` " -"permission." +"Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " +"and uploads :pep:`740`-compatible attestations for each distribution by " +"default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:182 -msgid "Finally, the signed distributions are uploaded to the GitHub Release." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:192 -msgid "" -"This is a replacement for GPG signatures, for which support has been " -"`removed from PyPI `_. " -"However, this job is not mandatory for uploading to PyPI and can be omitted." -msgstr "" - -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:172 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:174 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:210 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:184 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:214 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:188 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:190 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:224 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:198 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:226 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:200 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8760,7 +8726,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:234 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:208 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8769,7 +8735,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:242 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:216 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13690,7 +13656,7 @@ msgstr "" #: ../source/specifications/recording-installed-packages.rst:278 #: ../source/specifications/simple-repository-api.rst:993 #: ../source/specifications/source-distribution-format.rst:153 -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1269 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "歷史" @@ -23220,7 +23186,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:785 msgid "Version specifiers" msgstr "" @@ -23693,7 +23659,13 @@ msgid "" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:348 +#: ../source/specifications/version-specifiers.rst:346 +msgid "" +"Do note that development releases are considered a type of pre-release when " +"handling them." +msgstr "" + +#: ../source/specifications/version-specifiers.rst:351 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -23703,29 +23675,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:355 +#: ../source/specifications/version-specifiers.rst:358 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " "full maintenance releases which may include code changes." msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:364 #, fuzzy msgid "Version epochs" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:363 +#: ../source/specifications/version-specifiers.rst:366 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:371 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:370 +#: ../source/specifications/version-specifiers.rst:373 msgid "" "Most version identifiers will not include an epoch, as an explicit epoch is " "only needed if a project *changes* the way it handles version numbering in a " @@ -23736,18 +23708,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:384 +#: ../source/specifications/version-specifiers.rst:387 msgid "" "However, by specifying an explicit epoch, the sort order can be changed " "appropriately, as all versions from a later epoch are sorted after versions " "from an earlier epoch::" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:401 msgid "Normalization" msgstr "正規化" -#: ../source/specifications/version-specifiers.rst:400 +#: ../source/specifications/version-specifiers.rst:403 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -23755,23 +23727,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:410 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:409 +#: ../source/specifications/version-specifiers.rst:412 msgid "" "All ascii letters should be interpreted case insensitively within a version " "and the normal form is lowercase. This allows versions such as ``1.1RC1`` " "which would be normalized to ``1.1rc1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:418 #, fuzzy msgid "Integer Normalization" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:417 +#: ../source/specifications/version-specifiers.rst:420 msgid "" "All integers are interpreted via the ``int()`` built in and normalize to the " "string form of the output. This means that an integer version of ``00`` " @@ -23780,11 +23752,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:428 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:427 +#: ../source/specifications/version-specifiers.rst:430 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -23794,11 +23766,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:439 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:438 +#: ../source/specifications/version-specifiers.rst:441 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -23808,11 +23780,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:450 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:449 +#: ../source/specifications/version-specifiers.rst:452 msgid "" "Pre releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23820,11 +23792,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:458 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:457 +#: ../source/specifications/version-specifiers.rst:460 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -23835,11 +23807,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:469 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:468 +#: ../source/specifications/version-specifiers.rst:471 msgid "" "Post-releases allow the additional spellings of ``rev`` and ``r``. This " "allows versions such as ``1.0-r4`` which normalizes to ``1.0.post4``. As " @@ -23847,11 +23819,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:478 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:477 +#: ../source/specifications/version-specifiers.rst:480 msgid "" "Post releases allow omitting the numeral in which case it is implicitly " "assumed to be ``0``. The normal form for this is to include the ``0`` " @@ -23859,11 +23831,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:486 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:485 +#: ../source/specifications/version-specifiers.rst:488 msgid "" "Post releases allow omitting the ``post`` signifier all together. When using " "this form the separator MUST be ``-`` and no other form is allowed. This " @@ -23873,11 +23845,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:497 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:496 +#: ../source/specifications/version-specifiers.rst:499 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -23885,11 +23857,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:506 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:505 +#: ../source/specifications/version-specifiers.rst:508 msgid "" "Development releases allow omitting the numeral in which case it is " "implicitly assumed to be ``0``. The normal form for this is to include the " @@ -23897,11 +23869,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:515 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:514 +#: ../source/specifications/version-specifiers.rst:517 msgid "" "With a local version, in addition to the use of ``.`` as a separator of " "segments, the use of ``-`` and ``_`` is also acceptable. The normal form is " @@ -23909,11 +23881,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:524 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:523 +#: ../source/specifications/version-specifiers.rst:526 msgid "" "In order to support the common version notation of ``v1.0`` versions may be " "preceded by a single literal ``v`` character. This character MUST be ignored " @@ -23922,11 +23894,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:533 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:532 +#: ../source/specifications/version-specifiers.rst:535 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -23935,11 +23907,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:542 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:541 +#: ../source/specifications/version-specifiers.rst:544 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -23949,7 +23921,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:548 +#: ../source/specifications/version-specifiers.rst:551 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -23957,69 +23929,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:553 +#: ../source/specifications/version-specifiers.rst:556 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:562 +#: ../source/specifications/version-specifiers.rst:565 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:570 +#: ../source/specifications/version-specifiers.rst:573 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:582 +#: ../source/specifications/version-specifiers.rst:585 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:597 +#: ../source/specifications/version-specifiers.rst:600 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:611 +#: ../source/specifications/version-specifiers.rst:614 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:615 +#: ../source/specifications/version-specifiers.rst:618 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " "distributions deciding on a versioning scheme." msgstr "" -#: ../source/specifications/version-specifiers.rst:619 +#: ../source/specifications/version-specifiers.rst:622 msgid "" "The epoch segment of version identifiers MUST be sorted according to the " "numeric value of the given epoch. If no epoch segment is present, the " "implicit numeric value is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:623 +#: ../source/specifications/version-specifiers.rst:626 msgid "" "The release segment of version identifiers MUST be sorted in the same order " "as Python's tuple sorting when the normalized release segment is parsed as " "follows::" msgstr "" -#: ../source/specifications/version-specifiers.rst:629 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." msgstr "" -#: ../source/specifications/version-specifiers.rst:632 +#: ../source/specifications/version-specifiers.rst:635 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:637 +#: ../source/specifications/version-specifiers.rst:640 msgid "" "Note that ``c`` is considered to be semantically equivalent to ``rc`` and " "must be sorted as if it were ``rc``. Tools MAY reject the case of having the " @@ -24027,48 +23999,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:642 +#: ../source/specifications/version-specifiers.rst:645 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " "ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:648 +#: ../source/specifications/version-specifiers.rst:651 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:653 +#: ../source/specifications/version-specifiers.rst:656 msgid "" "Note that ``devN`` and ``postN`` MUST always be preceded by a dot, even when " "used immediately following a numeric version (e.g. ``1.0.dev456``, ``1.0." "post1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:657 +#: ../source/specifications/version-specifiers.rst:660 msgid "" "Within a pre-release, post-release or development release segment with a " "shared prefix, ordering MUST be by the value of the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:660 +#: ../source/specifications/version-specifiers.rst:663 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:688 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:687 +#: ../source/specifications/version-specifiers.rst:690 msgid "" "Metadata v1.0 (:pep:`241`) and metadata v1.1 (:pep:`314`) do not specify a " "standard version identification or ordering scheme. However metadata v1.2 (:" "pep:`345`) does specify a scheme which is defined in :pep:`386`." msgstr "" -#: ../source/specifications/version-specifiers.rst:691 +#: ../source/specifications/version-specifiers.rst:694 msgid "" "Due to the nature of the simple installer API it is not possible for an " "installer to be aware of which metadata version a particular distribution " @@ -24079,7 +24051,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:699 +#: ../source/specifications/version-specifiers.rst:702 msgid "" "Due to the above, this specification MUST be used for all versions of " "metadata and supersedes :pep:`386` even for metadata v1.2. Tools SHOULD " @@ -24089,17 +24061,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:705 +#: ../source/specifications/version-specifiers.rst:708 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:713 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:712 +#: ../source/specifications/version-specifiers.rst:715 msgid "" "Some projects may choose to use a version scheme which requires translation " "in order to comply with the public version scheme defined in this " @@ -24108,14 +24080,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:717 +#: ../source/specifications/version-specifiers.rst:720 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " "internal versioning scheme they prefer for their projects." msgstr "" -#: ../source/specifications/version-specifiers.rst:725 +#: ../source/specifications/version-specifiers.rst:728 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24126,7 +24098,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:732 +#: ../source/specifications/version-specifiers.rst:735 msgid "" "The \"Major.Minor.Patch\" (described in this specification as \"major.minor." "micro\") aspects of semantic versioning (clauses 1-8 in the 2.0.0 " @@ -24134,30 +24106,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:737 +#: ../source/specifications/version-specifiers.rst:740 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " "are not permitted in the public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:741 +#: ../source/specifications/version-specifiers.rst:744 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " "specify the appropriate version order." msgstr "" -#: ../source/specifications/version-specifiers.rst:745 +#: ../source/specifications/version-specifiers.rst:748 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:754 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:753 +#: ../source/specifications/version-specifiers.rst:756 msgid "" "Many build tools integrate with distributed version control systems like Git " "and Mercurial in order to add an identifying hash to the version identifier. " @@ -24165,30 +24137,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:758 +#: ../source/specifications/version-specifiers.rst:761 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " "based label can be stored in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:762 +#: ../source/specifications/version-specifiers.rst:765 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:769 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:768 +#: ../source/specifications/version-specifiers.rst:771 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " "character indicating the version of the database within that year." msgstr "" -#: ../source/specifications/version-specifiers.rst:772 +#: ../source/specifications/version-specifiers.rst:775 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24196,60 +24168,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:777 +#: ../source/specifications/version-specifiers.rst:780 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." msgstr "" -#: ../source/specifications/version-specifiers.rst:784 +#: ../source/specifications/version-specifiers.rst:787 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:792 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:794 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:795 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:796 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:797 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:795 +#: ../source/specifications/version-specifiers.rst:798 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:799 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:798 +#: ../source/specifications/version-specifiers.rst:801 msgid "" "The comma (\",\") is equivalent to a logical **and** operator: a candidate " "version must match all given version clauses in order to match the specifier " "as a whole." msgstr "" -#: ../source/specifications/version-specifiers.rst:802 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." msgstr "" -#: ../source/specifications/version-specifiers.rst:805 +#: ../source/specifications/version-specifiers.rst:808 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24258,79 +24230,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:811 +#: ../source/specifications/version-specifiers.rst:814 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " "entirely when checking if candidate versions match a given version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:823 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:822 +#: ../source/specifications/version-specifiers.rst:825 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " "expected to be compatible with the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:826 +#: ../source/specifications/version-specifiers.rst:829 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " "version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:830 +#: ../source/specifications/version-specifiers.rst:833 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" msgstr "" -#: ../source/specifications/version-specifiers.rst:835 +#: ../source/specifications/version-specifiers.rst:838 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:838 +#: ../source/specifications/version-specifiers.rst:841 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:846 +#: ../source/specifications/version-specifiers.rst:849 msgid "" "If a pre-release, post-release or developmental release is named in a " "compatible release clause as ``V.N.suffix``, then the suffix is ignored when " "determining the required prefix match::" msgstr "" -#: ../source/specifications/version-specifiers.rst:856 +#: ../source/specifications/version-specifiers.rst:859 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " "controlled by appending additional zeros to the version specifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:871 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:870 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:873 +#: ../source/specifications/version-specifiers.rst:876 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " "identifiers as described below." msgstr "" -#: ../source/specifications/version-specifiers.rst:877 +#: ../source/specifications/version-specifiers.rst:880 msgid "" "By default, the version matching operator is based on a strict equality " "comparison: the specified version must be exactly the same as the requested " @@ -24339,7 +24311,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:883 +#: ../source/specifications/version-specifiers.rst:886 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24347,7 +24319,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:888 +#: ../source/specifications/version-specifiers.rst:891 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24357,21 +24329,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:895 -#: ../source/specifications/version-specifiers.rst:956 +#: ../source/specifications/version-specifiers.rst:898 +#: ../source/specifications/version-specifiers.rst:959 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:902 +#: ../source/specifications/version-specifiers.rst:905 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " "following clauses would match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:910 +#: ../source/specifications/version-specifiers.rst:913 msgid "" "An exact match is also considered a prefix match (this interpretation is " "implied by the usual zero padding rules for the release segment of version " @@ -24379,7 +24351,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:922 +#: ../source/specifications/version-specifiers.rst:925 msgid "" "It is invalid to have a prefix match containing a development or local " "release such as ``1.0.dev1.*`` or ``1.0+foo1.*``. If present, the " @@ -24388,7 +24360,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:928 +#: ../source/specifications/version-specifiers.rst:931 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24398,14 +24370,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:935 +#: ../source/specifications/version-specifiers.rst:938 msgid "" "If the specified version identifier is a public version identifier (no local " "version label), then the local version label of any candidate versions MUST " "be ignored when matching versions." msgstr "" -#: ../source/specifications/version-specifiers.rst:939 +#: ../source/specifications/version-specifiers.rst:942 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24414,29 +24386,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:950 #, fuzzy msgid "Version exclusion" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:949 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:952 +#: ../source/specifications/version-specifiers.rst:955 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " "match is inverted." msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:968 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:967 +#: ../source/specifications/version-specifiers.rst:970 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -24445,27 +24417,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 +#: ../source/specifications/version-specifiers.rst:976 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:975 -#: ../source/specifications/version-specifiers.rst:1005 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." msgstr "" -#: ../source/specifications/version-specifiers.rst:978 -#: ../source/specifications/version-specifiers.rst:1008 +#: ../source/specifications/version-specifiers.rst:981 +#: ../source/specifications/version-specifiers.rst:1011 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:985 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:984 +#: ../source/specifications/version-specifiers.rst:987 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -24475,7 +24447,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:990 +#: ../source/specifications/version-specifiers.rst:993 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release of " "the given version unless ``V`` itself is a post release. You may mandate " @@ -24485,13 +24457,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:997 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:1000 +#: ../source/specifications/version-specifiers.rst:1003 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1129 +#: ../source/specifications/version-specifiers.rst:1132 msgid "" "For version control references, the ``VCS+protocol`` scheme SHOULD be used " "to identify both the version control system and the secure transport, and a " @@ -24711,7 +24683,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1135 +#: ../source/specifications/version-specifiers.rst:1138 msgid "" "To handle version control systems that do not support including commit or " "tag references directly in the URL, that information may be appended to the " @@ -24719,7 +24691,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1142 +#: ../source/specifications/version-specifiers.rst:1145 msgid "" "This isn't *quite* the same as the existing VCS reference notation supported " "by pip. Firstly, the distribution name is moved in front rather than " @@ -24730,15 +24702,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1150 +#: ../source/specifications/version-specifiers.rst:1153 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1161 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1160 +#: ../source/specifications/version-specifiers.rst:1163 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -24746,7 +24718,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1165 +#: ../source/specifications/version-specifiers.rst:1168 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -24754,7 +24726,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1170 +#: ../source/specifications/version-specifiers.rst:1173 msgid "" "On Windows the file format should include the drive letter if applicable as " "part of the ```` (e.g. ``file:///c:/path/to/a/file``). Unlike \\*nix " @@ -24766,43 +24738,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1184 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1183 +#: ../source/specifications/version-specifiers.rst:1186 msgid "" "Note: this comparison is to ``pkg_resources.parse_version`` as it existed at " "the time :pep:`440` was written. After the PEP was accepted, setuptools 6.0 " "and later versions adopted the behaviour described here." msgstr "" -#: ../source/specifications/version-specifiers.rst:1187 +#: ../source/specifications/version-specifiers.rst:1190 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " "``pkg_resources.parse_version`` considers it a pre-release marker." msgstr "" -#: ../source/specifications/version-specifiers.rst:1191 +#: ../source/specifications/version-specifiers.rst:1194 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " "meaning from *any* arbitrary string." msgstr "" -#: ../source/specifications/version-specifiers.rst:1195 +#: ../source/specifications/version-specifiers.rst:1198 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " "only a single use of each type and they must exist in a certain order." msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1207 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1206 +#: ../source/specifications/version-specifiers.rst:1209 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -24811,23 +24783,29 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1212 +#: ../source/specifications/version-specifiers.rst:1215 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1221 +#: ../source/specifications/version-specifiers.rst:1224 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_ project):" msgstr "" -#: ../source/specifications/version-specifiers.rst:1268 +#: ../source/specifications/version-specifiers.rst:1271 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" +#: ../source/specifications/version-specifiers.rst:1272 +msgid "" +"May 2025: Clarify that development releases are a form of pre-release when " +"they are handled." +msgstr "" + #: ../source/specifications/virtual-environments.rst:6 msgid "Python Virtual Environments" msgstr ""