From 039368675da57367bee03446489f1a54c33f5065 Mon Sep 17 00:00:00 2001 From: Hosted Weblate Date: Sun, 3 Nov 2024 07:00:29 +0100 Subject: [PATCH 1/4] Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Co-authored-by: Hosted Weblate Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ Translation: pypa/packaging.python.org --- locales/ar/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/ars/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/de/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/eo/LC_MESSAGES/messages.po | 1167 ++++++++++++++-------- locales/es/LC_MESSAGES/messages.po | 1168 ++++++++++++++-------- locales/fa/LC_MESSAGES/messages.po | 1161 ++++++++++++++-------- locales/fil/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/fr/LC_MESSAGES/messages.po | 1164 ++++++++++++++-------- locales/frc/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/gl/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/gmh/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/hi/LC_MESSAGES/messages.po | 1161 ++++++++++++++-------- locales/id/LC_MESSAGES/messages.po | 1161 ++++++++++++++-------- locales/ko/LC_MESSAGES/messages.po | 1163 ++++++++++++++-------- locales/lzh/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/mk/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/pl/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/pt_BR/LC_MESSAGES/messages.po | 1210 ++++++++++++++-------- locales/ro/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/ru/LC_MESSAGES/messages.po | 1215 +++++++++++++++-------- locales/sai/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/si/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/sk/LC_MESSAGES/messages.po | 1161 ++++++++++++++-------- locales/ta/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/tr/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/uk/LC_MESSAGES/messages.po | 1174 ++++++++++++++-------- locales/vi/LC_MESSAGES/messages.po | 1159 +++++++++++++-------- locales/zh_Hans/LC_MESSAGES/messages.po | 1171 ++++++++++++++-------- locales/zh_Hant/LC_MESSAGES/messages.po | 1163 ++++++++++++++-------- 29 files changed, 21971 insertions(+), 11812 deletions(-) diff --git a/locales/ar/LC_MESSAGES/messages.po b/locales/ar/LC_MESSAGES/messages.po index 8275a456c..ff65aaf99 100644 --- a/locales/ar/LC_MESSAGES/messages.po +++ b/locales/ar/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-01-18 07:31+0000\n" "Last-Translator: Youcef Guenaoua \n" "Language-Team: Arabic `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3176,13 +3175,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8654,7 +8654,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8854,45 +8854,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12170,7 +12200,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12179,11 +12209,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12305,15 +12335,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12412,16 +12442,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12612,94 +12642,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12707,7 +12718,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12717,33 +12728,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12751,50 +12762,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12802,64 +12813,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12867,13 +12878,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12881,36 +12892,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12919,13 +12938,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12933,20 +12952,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12954,7 +12973,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12964,11 +12983,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12976,7 +12995,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12986,18 +13005,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13006,7 +13025,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13017,63 +13036,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13084,33 +13128,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13119,89 +13163,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16111,7 +16155,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16363,24 +16407,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16388,14 +16433,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16403,7 +16448,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16411,24 +16456,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16436,7 +16481,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16447,17 +16492,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16465,19 +16510,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16486,20 +16531,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16507,18 +16552,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16526,7 +16571,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16534,14 +16579,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18577,7 +18622,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18910,29 +18955,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18940,48 +18985,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18989,7 +19034,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18997,11 +19042,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19009,11 +19054,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19021,20 +19066,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19043,13 +19088,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19059,28 +19104,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19091,18 +19136,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19110,22 +19155,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19134,11 +19179,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19148,11 +19193,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19162,11 +19207,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19174,11 +19219,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19189,11 +19234,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19201,11 +19246,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19213,11 +19258,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19227,11 +19272,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19239,11 +19284,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19251,11 +19296,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19263,11 +19308,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19276,11 +19321,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19289,11 +19334,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19303,7 +19348,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19311,69 +19356,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19381,48 +19426,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19433,7 +19478,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19443,17 +19488,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19462,14 +19507,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19480,7 +19525,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19488,30 +19533,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19519,30 +19564,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19550,60 +19595,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19612,79 +19657,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19693,7 +19738,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19701,7 +19746,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19711,21 +19756,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19733,7 +19778,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19742,7 +19787,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19752,14 +19797,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19768,28 +19813,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19798,27 +19843,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19828,7 +19873,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19838,13 +19883,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20064,7 +20109,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20072,7 +20117,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20083,15 +20128,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20099,7 +20144,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20107,7 +20152,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20119,43 +20164,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20164,20 +20209,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20255,6 +20300,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/ars/LC_MESSAGES/messages.po b/locales/ars/LC_MESSAGES/messages.po index 8355433ce..85344bb15 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/de/LC_MESSAGES/messages.po b/locales/de/LC_MESSAGES/messages.po index 9a67d94b6..3c2f0956f 100644 --- a/locales/de/LC_MESSAGES/messages.po +++ b/locales/de/LC_MESSAGES/messages.po @@ -13,7 +13,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-10-17 21:16+0000\n" "Last-Translator: Emr \n" "Language-Team: German `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3242,13 +3241,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8733,7 +8733,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8933,45 +8933,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12249,7 +12279,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12258,11 +12288,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12384,15 +12414,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12491,16 +12521,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12691,94 +12721,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Betreuer" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12786,7 +12797,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12796,33 +12807,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12830,50 +12841,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12881,64 +12892,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12946,13 +12957,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12960,36 +12971,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12998,13 +13017,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13012,20 +13031,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13033,7 +13052,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13043,11 +13062,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13055,7 +13074,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13065,18 +13084,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13085,7 +13104,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13096,63 +13115,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13163,33 +13207,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13198,89 +13242,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16198,7 +16242,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16451,24 +16495,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16476,14 +16521,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16491,7 +16536,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16499,24 +16544,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16524,7 +16569,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16535,17 +16580,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16553,19 +16598,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16574,20 +16619,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16595,18 +16640,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16614,7 +16659,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16622,14 +16667,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18666,7 +18711,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18999,29 +19044,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19029,48 +19074,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19078,7 +19123,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19086,11 +19131,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19098,11 +19143,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19110,20 +19155,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19132,13 +19177,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19148,28 +19193,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19180,18 +19225,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19199,22 +19244,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19223,11 +19268,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19237,11 +19282,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19251,11 +19296,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19263,11 +19308,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19278,11 +19323,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19290,11 +19335,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19302,11 +19347,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19316,11 +19361,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19328,11 +19373,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19340,11 +19385,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19352,11 +19397,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19365,11 +19410,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19378,11 +19423,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19392,7 +19437,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19400,69 +19445,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19470,48 +19515,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19522,7 +19567,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19532,17 +19577,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19551,14 +19596,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19569,7 +19614,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19577,30 +19622,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19608,30 +19653,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19639,60 +19684,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19701,79 +19746,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19782,7 +19827,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19790,7 +19835,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19800,21 +19845,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19822,7 +19867,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19831,7 +19876,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19841,14 +19886,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19857,28 +19902,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19887,27 +19932,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19917,7 +19962,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19927,13 +19972,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20153,7 +20198,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20161,7 +20206,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20172,15 +20217,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20188,7 +20233,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20196,7 +20241,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20208,43 +20253,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20253,20 +20298,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20344,6 +20389,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/eo/LC_MESSAGES/messages.po b/locales/eo/LC_MESSAGES/messages.po index 1988c16a3..f008b02dc 100644 --- a/locales/eo/LC_MESSAGES/messages.po +++ b/locales/eo/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2021-08-06 05:45+0000\n" "Last-Translator: meowmeowmeowcat \n" "Language-Team: Esperanto `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3262,13 +3261,14 @@ msgstr "Kolumno" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Priskribo" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Ekzemploj" @@ -8869,7 +8869,7 @@ msgid "Dependencies and requirements" msgstr "install_requires kontraste kun requirements.txt" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "``dependencies``/``optional-dependencies``" @@ -9072,46 +9072,76 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "``urls``" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 #, fuzzy msgid "A full example" msgstr "Ekzemploj" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12538,7 +12568,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12547,11 +12577,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12673,15 +12703,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12780,16 +12810,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12980,94 +13010,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Prizorganto" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -13075,7 +13086,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -13085,33 +13096,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -13119,50 +13130,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -13170,64 +13181,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13235,13 +13246,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13249,36 +13260,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13287,13 +13306,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13301,20 +13320,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13322,7 +13341,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13332,11 +13351,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "Malofte uzataj kampoj" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13344,7 +13363,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13354,18 +13373,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13374,7 +13393,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13385,67 +13404,92 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 #, fuzzy #| msgid "Rarely Used Fields" msgid "Deprecated Fields" msgstr "Malofte uzataj kampoj" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 #, fuzzy #| msgid "Requirements files" msgid "Requires" msgstr "Dosiero requirements.txt" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13456,33 +13500,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13491,90 +13535,90 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 #, fuzzy msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "Marklingvo reStructuredText: http://docutils.sourceforge.net/" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16529,7 +16573,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "``dynamic``" @@ -16784,24 +16828,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16809,14 +16854,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16824,7 +16869,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16832,24 +16877,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16857,7 +16902,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16868,17 +16913,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "Tipo de TOML_: listo de signoĉenoj" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16886,19 +16931,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16907,20 +16952,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16928,18 +16973,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16947,7 +16992,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16955,14 +17000,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -19018,7 +19063,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19356,29 +19401,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19386,48 +19431,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19435,7 +19480,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19443,11 +19488,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19455,11 +19500,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19467,20 +19512,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19489,13 +19534,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19505,29 +19550,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Versio" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19538,18 +19583,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19557,23 +19602,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Versio de pako" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19582,11 +19627,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19596,11 +19641,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19610,11 +19655,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19622,11 +19667,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19637,11 +19682,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19649,11 +19694,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19661,11 +19706,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19675,11 +19720,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19687,11 +19732,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19699,11 +19744,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19711,11 +19756,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19724,11 +19769,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19737,11 +19782,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19751,7 +19796,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19759,69 +19804,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19829,48 +19874,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19881,7 +19926,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19891,17 +19936,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19910,14 +19955,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19928,7 +19973,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19936,30 +19981,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19967,30 +20012,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19998,60 +20043,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -20060,81 +20105,81 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 #, fuzzy #| msgid "Version" msgid "Version matching" msgstr "Versio" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -20143,7 +20188,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -20151,7 +20196,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -20161,21 +20206,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -20183,7 +20228,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -20192,7 +20237,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -20202,14 +20247,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -20218,30 +20263,30 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy #| msgid "Version Specifier" msgid "Version exclusion" msgstr "Versio-Specifilo" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -20250,27 +20295,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -20280,7 +20325,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20290,13 +20335,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20516,7 +20561,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20524,7 +20569,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20535,16 +20580,16 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 #, fuzzy msgid "Remote URL examples::" msgstr "Ekzemploj" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20552,7 +20597,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20560,7 +20605,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20572,43 +20617,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20617,20 +20662,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20710,6 +20755,314 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "Nomo de projekto" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Versio de pako" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +#, fuzzy +#| msgid "Creating pyproject.toml" +msgid "``documentation`` (Documentation)" +msgstr "Krei la dosieron pyproject.toml" + +#: ../source/specifications/well-known-project-urls.rst:124 +#, fuzzy +#| msgid "Creating pyproject.toml" +msgid "The project's online documentation" +msgstr "Krei la dosieron pyproject.toml" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +msgid "Example behavior" +msgstr "Ekzemploj" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/es/LC_MESSAGES/messages.po b/locales/es/LC_MESSAGES/messages.po index 057492da5..fa3975df2 100644 --- a/locales/es/LC_MESSAGES/messages.po +++ b/locales/es/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-09-17 19:22+0000\n" "Last-Translator: gallegonovato \n" "Language-Team: Spanish `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3395,13 +3394,14 @@ msgstr "Columna" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Descripción" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Ejemplos" @@ -8929,7 +8929,7 @@ msgid "Dependencies and requirements" msgstr "Archivos de requisitos" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -9130,45 +9130,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "Ejemplo completo" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12458,7 +12488,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12467,11 +12497,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12593,15 +12623,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12700,16 +12730,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12900,94 +12930,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Responsable" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12995,7 +13006,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -13005,33 +13016,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -13039,50 +13050,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -13090,64 +13101,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13155,13 +13166,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13169,36 +13180,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13207,13 +13226,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13221,20 +13240,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13242,7 +13261,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13252,11 +13271,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13264,7 +13283,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13274,18 +13293,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13294,7 +13313,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13305,64 +13324,89 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 #, fuzzy msgid "Requires" msgstr "Archivo de requisitos" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13373,33 +13417,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13408,89 +13452,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16421,7 +16465,7 @@ msgid "``dependencies``" msgstr "Dependencias externas" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16677,24 +16721,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16702,14 +16747,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16717,7 +16762,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16725,24 +16770,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16750,7 +16795,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16761,17 +16806,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16779,19 +16824,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16800,20 +16845,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16821,18 +16866,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16840,7 +16885,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16848,14 +16893,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18916,7 +18961,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19251,29 +19296,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19281,48 +19326,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19330,7 +19375,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19338,11 +19383,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19350,11 +19395,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19362,20 +19407,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19384,13 +19429,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19400,29 +19445,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19433,19 +19478,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "Traducciones" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19453,23 +19498,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Traducciones" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19478,11 +19523,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19492,11 +19537,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19506,11 +19551,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19518,11 +19563,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19533,11 +19578,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19545,11 +19590,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19557,11 +19602,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19571,11 +19616,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19583,11 +19628,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19595,11 +19640,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19607,11 +19652,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19620,11 +19665,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19633,11 +19678,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19647,7 +19692,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19655,69 +19700,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19725,48 +19770,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19777,7 +19822,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19787,17 +19832,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19806,14 +19851,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19824,7 +19869,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19832,30 +19877,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19863,30 +19908,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19894,60 +19939,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19956,80 +20001,80 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 #, fuzzy msgid "Version matching" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -20038,7 +20083,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -20046,7 +20091,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -20056,21 +20101,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -20078,7 +20123,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -20087,7 +20132,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -20097,14 +20142,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -20113,29 +20158,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "Versión" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -20144,27 +20189,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -20174,7 +20219,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20184,13 +20229,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20410,7 +20455,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20418,7 +20463,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20429,16 +20474,16 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 #, fuzzy msgid "Remote URL examples::" msgstr "Por ejemplo::" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20446,7 +20491,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20454,7 +20499,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20466,43 +20511,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20511,20 +20556,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20604,6 +20649,315 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +msgid "Well-known Project URLs in Metadata" +msgstr "Nombre de proyecto" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Traducciones" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "Traducciones" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +#, fuzzy +msgid "``documentation`` (Documentation)" +msgstr "Creación de documentación" + +#: ../source/specifications/well-known-project-urls.rst:124 +#, fuzzy +msgid "The project's online documentation" +msgstr "Creación de documentación" + +#: ../source/specifications/well-known-project-urls.rst:125 +#, fuzzy +#| msgid "``upload_docs``" +msgid "``docs``" +msgstr "``upload_docs``" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +msgid "Funding Information" +msgstr "Configuraciones habituales" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +msgid "Example behavior" +msgstr "Ejemplos" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "Cómo obtener asistencia" diff --git a/locales/fa/LC_MESSAGES/messages.po b/locales/fa/LC_MESSAGES/messages.po index ef3d7fd23..d62cf6ae5 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2023-02-15 07:52+0000\n" "Last-Translator: Arsalan Dehghani \n" "Language-Team: Persian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3182,13 +3181,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8675,7 +8675,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8875,45 +8875,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12191,7 +12221,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12200,11 +12230,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12326,15 +12356,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12433,16 +12463,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12633,94 +12663,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12728,7 +12739,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12738,33 +12749,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12772,50 +12783,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12823,64 +12834,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12888,13 +12899,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12902,36 +12913,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12940,13 +12959,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12954,20 +12973,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12975,7 +12994,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12985,11 +13004,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12997,7 +13016,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13007,18 +13026,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13027,7 +13046,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13038,63 +13057,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13105,33 +13149,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13140,89 +13184,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16135,7 +16179,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16387,24 +16431,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16412,14 +16457,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16427,7 +16472,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16435,24 +16480,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16460,7 +16505,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16471,17 +16516,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16489,19 +16534,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16510,20 +16555,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16531,18 +16576,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16550,7 +16595,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16558,14 +16603,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18606,7 +18651,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18942,29 +18987,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18972,48 +19017,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19021,7 +19066,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19029,11 +19074,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19041,11 +19086,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19053,20 +19098,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19075,13 +19120,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19091,29 +19136,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19124,19 +19169,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19144,23 +19189,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19169,11 +19214,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19183,11 +19228,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19197,11 +19242,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19209,11 +19254,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19224,11 +19269,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19236,11 +19281,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19248,11 +19293,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19262,11 +19307,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19274,11 +19319,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19286,11 +19331,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19298,11 +19343,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19311,11 +19356,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19324,11 +19369,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19338,7 +19383,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19346,69 +19391,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19416,48 +19461,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19468,7 +19513,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19478,17 +19523,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19497,14 +19542,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19515,7 +19560,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19523,30 +19568,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19554,30 +19599,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19585,60 +19630,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19647,79 +19692,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19728,7 +19773,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19736,7 +19781,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19746,21 +19791,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19768,7 +19813,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19777,7 +19822,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19787,14 +19832,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19803,29 +19848,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "ترجمه‌ها" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19834,27 +19879,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19864,7 +19909,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19874,13 +19919,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20100,7 +20145,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20108,7 +20153,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20119,15 +20164,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20135,7 +20180,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20143,7 +20188,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20155,43 +20200,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20200,20 +20245,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20291,6 +20336,308 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "ترجمه‌ها" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "ترجمه‌ها" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/fil/LC_MESSAGES/messages.po b/locales/fil/LC_MESSAGES/messages.po index 79e43708e..7a27483c0 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2022-11-19 08:28+0000\n" "Last-Translator: RedFurrFox \n" "Language-Team: Filipino `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3177,13 +3176,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8655,7 +8655,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8855,45 +8855,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12171,7 +12201,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12180,11 +12210,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12306,15 +12336,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12413,16 +12443,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12613,94 +12643,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12708,7 +12719,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12718,33 +12729,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12752,50 +12763,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12803,64 +12814,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12868,13 +12879,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12882,36 +12893,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12920,13 +12939,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12934,20 +12953,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12955,7 +12974,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12965,11 +12984,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12977,7 +12996,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12987,18 +13006,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13007,7 +13026,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13018,63 +13037,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13085,33 +13129,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13120,89 +13164,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16112,7 +16156,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16364,24 +16408,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16389,14 +16434,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16404,7 +16449,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16412,24 +16457,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16437,7 +16482,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16448,17 +16493,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16466,19 +16511,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16487,20 +16532,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16508,18 +16553,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16527,7 +16572,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16535,14 +16580,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18578,7 +18623,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18911,29 +18956,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18941,48 +18986,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18990,7 +19035,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18998,11 +19043,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19010,11 +19055,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19022,20 +19067,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19044,13 +19089,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19060,28 +19105,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19092,18 +19137,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19111,22 +19156,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19135,11 +19180,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19149,11 +19194,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19163,11 +19208,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19175,11 +19220,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19190,11 +19235,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19202,11 +19247,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19214,11 +19259,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19228,11 +19273,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19240,11 +19285,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19252,11 +19297,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19264,11 +19309,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19277,11 +19322,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19290,11 +19335,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19304,7 +19349,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19312,69 +19357,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19382,48 +19427,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19434,7 +19479,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19444,17 +19489,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19463,14 +19508,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19481,7 +19526,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19489,30 +19534,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19520,30 +19565,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19551,60 +19596,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19613,79 +19658,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19694,7 +19739,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19702,7 +19747,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19712,21 +19757,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19734,7 +19779,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19743,7 +19788,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19753,14 +19798,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19769,28 +19814,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19799,27 +19844,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19829,7 +19874,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19839,13 +19884,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20065,7 +20110,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20073,7 +20118,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20084,15 +20129,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20100,7 +20145,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20108,7 +20153,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20120,43 +20165,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20165,20 +20210,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20256,6 +20301,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/fr/LC_MESSAGES/messages.po b/locales/fr/LC_MESSAGES/messages.po index 9f0f8e54e..7c09df79a 100644 --- a/locales/fr/LC_MESSAGES/messages.po +++ b/locales/fr/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-09-21 00:40+0000\n" "Last-Translator: Pierre PETAT \n" "Language-Team: French `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3343,13 +3342,14 @@ msgstr "Colonne" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Description" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Exemples" @@ -8863,7 +8863,7 @@ msgid "Dependencies and requirements" msgstr "Fichiers requirements vs install_requires" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -9067,46 +9067,76 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 #, fuzzy msgid "A full example" msgstr "Exemples" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12389,7 +12419,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12398,11 +12428,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12524,15 +12554,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12631,16 +12661,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12831,94 +12861,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12926,7 +12937,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12936,33 +12947,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12970,50 +12981,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -13021,64 +13032,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13086,13 +13097,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13100,36 +13111,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13138,13 +13157,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13152,20 +13171,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13173,7 +13192,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13183,11 +13202,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13195,7 +13214,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13205,18 +13224,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13225,7 +13244,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13236,63 +13255,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13303,33 +13347,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13338,89 +13382,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16352,7 +16396,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16604,24 +16648,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16629,14 +16674,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16644,7 +16689,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16652,24 +16697,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16677,7 +16722,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16688,17 +16733,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16706,19 +16751,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16727,20 +16772,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16748,18 +16793,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16767,7 +16812,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16775,14 +16820,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18829,7 +18874,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19164,30 +19209,30 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 #, fuzzy msgid "Pre-releases" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19195,49 +19240,49 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 #, fuzzy msgid "Post-releases" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19245,7 +19290,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19253,11 +19298,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19265,11 +19310,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19277,20 +19322,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19299,13 +19344,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19315,29 +19360,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19348,19 +19393,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19368,23 +19413,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19393,11 +19438,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19407,11 +19452,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19421,11 +19466,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19433,11 +19478,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19448,11 +19493,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19460,11 +19505,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19472,11 +19517,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19486,11 +19531,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19498,11 +19543,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19510,11 +19555,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19522,11 +19567,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19535,11 +19580,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19548,11 +19593,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19562,7 +19607,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19570,69 +19615,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19640,48 +19685,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19692,7 +19737,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19702,17 +19747,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19721,14 +19766,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19739,7 +19784,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19747,30 +19792,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19778,30 +19823,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19809,60 +19854,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19871,79 +19916,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19952,7 +19997,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19960,7 +20005,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19970,21 +20015,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19992,7 +20037,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -20001,7 +20046,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -20011,14 +20056,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -20027,29 +20072,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "Traductions" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -20058,27 +20103,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -20088,7 +20133,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20098,13 +20143,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20325,7 +20370,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20333,7 +20378,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20344,16 +20389,16 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 #, fuzzy msgid "Remote URL examples::" msgstr "Exemples" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20361,7 +20406,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20369,7 +20414,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20381,43 +20426,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20426,20 +20471,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20518,6 +20563,311 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +msgid "Well-known Project URLs in Metadata" +msgstr "Nom du projet" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Traductions" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "Traductions" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +msgid "Funding Information" +msgstr "Outils supplémentaires" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +msgid "Example behavior" +msgstr "Exemples" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/frc/LC_MESSAGES/messages.po b/locales/frc/LC_MESSAGES/messages.po index 4d4b6adc2..4f77809ca 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/gl/LC_MESSAGES/messages.po b/locales/gl/LC_MESSAGES/messages.po index 69e136939..0388a8a23 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/gmh/LC_MESSAGES/messages.po b/locales/gmh/LC_MESSAGES/messages.po index bd35aebf7..0328bdb58 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/hi/LC_MESSAGES/messages.po b/locales/hi/LC_MESSAGES/messages.po index ea7372987..bdd3fc82d 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-09-16 10:09+0000\n" "Last-Translator: kumar Shivam \n" "Language-Team: Hindi `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3195,13 +3194,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8703,7 +8703,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8903,45 +8903,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12219,7 +12249,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12228,11 +12258,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12354,15 +12384,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12461,16 +12491,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12661,94 +12691,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12756,7 +12767,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12766,33 +12777,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12800,50 +12811,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12851,64 +12862,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12916,13 +12927,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12930,36 +12941,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12968,13 +12987,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12982,20 +13001,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13003,7 +13022,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13013,11 +13032,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13025,7 +13044,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13035,18 +13054,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13055,7 +13074,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13066,63 +13085,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13133,33 +13177,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13168,89 +13212,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16165,7 +16209,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16417,24 +16461,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16442,14 +16487,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16457,7 +16502,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16465,24 +16510,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16490,7 +16535,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16501,17 +16546,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16519,19 +16564,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16540,20 +16585,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16561,18 +16606,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16580,7 +16625,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16588,14 +16633,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18637,7 +18682,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18970,29 +19015,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19000,48 +19045,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19049,7 +19094,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19057,11 +19102,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19069,11 +19114,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19081,20 +19126,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19103,13 +19148,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19119,28 +19164,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19151,18 +19196,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19170,22 +19215,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19194,11 +19239,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19208,11 +19253,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19222,11 +19267,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19234,11 +19279,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19249,11 +19294,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19261,11 +19306,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19273,11 +19318,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19287,11 +19332,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19299,11 +19344,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19311,11 +19356,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19323,11 +19368,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19336,11 +19381,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19349,11 +19394,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19363,7 +19408,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19371,69 +19416,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19441,48 +19486,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19493,7 +19538,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19503,17 +19548,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19522,14 +19567,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19540,7 +19585,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19548,30 +19593,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19579,30 +19624,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19610,60 +19655,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19672,79 +19717,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19753,7 +19798,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19761,7 +19806,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19771,21 +19816,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19793,7 +19838,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19802,7 +19847,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19812,14 +19857,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19828,28 +19873,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19858,27 +19903,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19888,7 +19933,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19898,13 +19943,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20124,7 +20169,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20132,7 +20177,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20143,15 +20188,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20159,7 +20204,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20167,7 +20212,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20179,43 +20224,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20224,20 +20269,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20315,6 +20360,308 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "परियोजना" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/id/LC_MESSAGES/messages.po b/locales/id/LC_MESSAGES/messages.po index 77ba3e118..22531d1eb 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-10-17 21:16+0000\n" "Last-Translator: oon arfiandwi \n" "Language-Team: Indonesian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3216,13 +3215,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8709,7 +8709,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8909,45 +8909,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12225,7 +12255,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12234,11 +12264,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12360,15 +12390,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12467,16 +12497,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12667,94 +12697,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12762,7 +12773,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12772,33 +12783,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12806,50 +12817,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12857,64 +12868,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12922,13 +12933,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12936,36 +12947,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12974,13 +12993,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12988,20 +13007,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13009,7 +13028,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13019,11 +13038,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13031,7 +13050,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13041,18 +13060,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13061,7 +13080,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13072,63 +13091,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13139,33 +13183,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13174,89 +13218,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16173,7 +16217,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16425,24 +16469,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16450,14 +16495,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16465,7 +16510,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16473,24 +16518,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16498,7 +16543,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16509,17 +16554,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16527,19 +16572,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16548,20 +16593,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16569,18 +16614,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16588,7 +16633,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16596,14 +16641,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18644,7 +18689,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18980,29 +19025,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19010,48 +19055,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19059,7 +19104,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19067,11 +19112,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19079,11 +19124,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19091,20 +19136,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19113,13 +19158,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19129,29 +19174,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19162,19 +19207,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19182,23 +19227,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19207,11 +19252,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19221,11 +19266,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19235,11 +19280,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19247,11 +19292,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19262,11 +19307,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19274,11 +19319,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19286,11 +19331,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19300,11 +19345,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19312,11 +19357,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19324,11 +19369,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19336,11 +19381,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19349,11 +19394,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19362,11 +19407,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19376,7 +19421,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19384,69 +19429,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19454,48 +19499,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19506,7 +19551,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19516,17 +19561,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19535,14 +19580,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19553,7 +19598,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19561,30 +19606,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19592,30 +19637,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19623,60 +19668,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19685,79 +19730,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19766,7 +19811,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19774,7 +19819,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19784,21 +19829,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19806,7 +19851,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19815,7 +19860,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19825,14 +19870,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19841,29 +19886,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "Penerjemahan" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19872,27 +19917,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19902,7 +19947,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19912,13 +19957,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20138,7 +20183,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20146,7 +20191,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20157,15 +20202,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20173,7 +20218,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20181,7 +20226,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20193,43 +20238,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20238,20 +20283,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20329,6 +20374,308 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Penerjemahan" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "Penerjemahan" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index 5a31a1d52..f1f5f7f42 100644 --- a/locales/ko/LC_MESSAGES/messages.po +++ b/locales/ko/LC_MESSAGES/messages.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-03-21 03:01+0000\n" "Last-Translator: emscb \n" "Language-Team: Korean `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3245,13 +3244,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8744,7 +8744,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8944,45 +8944,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12260,7 +12290,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12269,11 +12299,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12395,15 +12425,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12502,16 +12532,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12702,94 +12732,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "관리자" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12797,7 +12808,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12807,33 +12818,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12841,50 +12852,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12892,64 +12903,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12957,13 +12968,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12971,36 +12982,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13009,13 +13028,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13023,20 +13042,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13044,7 +13063,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13054,11 +13073,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13066,7 +13085,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13076,18 +13095,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13096,7 +13115,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13107,63 +13126,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13174,33 +13218,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13209,89 +13253,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16209,7 +16253,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16461,24 +16505,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16486,14 +16531,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16501,7 +16546,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16509,24 +16554,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16534,7 +16579,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16545,17 +16590,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16563,19 +16608,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16584,20 +16629,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16605,18 +16650,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16624,7 +16669,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16632,14 +16677,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18684,7 +18729,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19019,29 +19064,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19049,48 +19094,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19098,7 +19143,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19106,11 +19151,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19118,11 +19163,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19130,20 +19175,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19152,13 +19197,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19168,29 +19213,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19201,19 +19246,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19221,23 +19266,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19246,11 +19291,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19260,11 +19305,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19274,11 +19319,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19286,11 +19331,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19301,11 +19346,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19313,11 +19358,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19325,11 +19370,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19339,11 +19384,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19351,11 +19396,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19363,11 +19408,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19375,11 +19420,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19388,11 +19433,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19401,11 +19446,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19415,7 +19460,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19423,69 +19468,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19493,48 +19538,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19545,7 +19590,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19555,17 +19600,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19574,14 +19619,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19592,7 +19637,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19600,30 +19645,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19631,30 +19676,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19662,60 +19707,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19724,79 +19769,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19805,7 +19850,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19813,7 +19858,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19823,21 +19868,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19845,7 +19890,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19854,7 +19899,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19864,14 +19909,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19880,29 +19925,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "번역" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19911,27 +19956,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19941,7 +19986,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19951,13 +19996,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20177,7 +20222,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20185,7 +20230,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20196,15 +20241,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20212,7 +20257,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20220,7 +20265,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20232,43 +20277,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20277,20 +20322,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20368,6 +20413,310 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "프로젝트 이름" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "번역" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "번역" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/lzh/LC_MESSAGES/messages.po b/locales/lzh/LC_MESSAGES/messages.po index 6c4f6e423..dc79a204f 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-01-31 06:01+0000\n" "Last-Translator: maker \n" "Language-Team: Chinese (Literary) `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3177,13 +3176,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8655,7 +8655,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8855,45 +8855,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12171,7 +12201,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12180,11 +12210,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12306,15 +12336,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12413,16 +12443,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12613,94 +12643,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12708,7 +12719,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12718,33 +12729,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12752,50 +12763,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12803,64 +12814,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12868,13 +12879,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12882,36 +12893,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12920,13 +12939,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12934,20 +12953,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12955,7 +12974,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12965,11 +12984,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12977,7 +12996,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12987,18 +13006,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13007,7 +13026,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13018,63 +13037,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13085,33 +13129,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13120,89 +13164,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16112,7 +16156,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16364,24 +16408,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16389,14 +16434,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16404,7 +16449,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16412,24 +16457,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16437,7 +16482,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16448,17 +16493,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16466,19 +16511,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16487,20 +16532,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16508,18 +16553,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16527,7 +16572,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16535,14 +16580,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18578,7 +18623,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18911,29 +18956,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18941,48 +18986,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18990,7 +19035,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18998,11 +19043,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19010,11 +19055,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19022,20 +19067,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19044,13 +19089,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19060,28 +19105,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19092,18 +19137,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19111,22 +19156,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19135,11 +19180,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19149,11 +19194,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19163,11 +19208,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19175,11 +19220,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19190,11 +19235,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19202,11 +19247,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19214,11 +19259,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19228,11 +19273,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19240,11 +19285,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19252,11 +19297,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19264,11 +19309,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19277,11 +19322,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19290,11 +19335,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19304,7 +19349,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19312,69 +19357,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19382,48 +19427,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19434,7 +19479,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19444,17 +19489,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19463,14 +19508,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19481,7 +19526,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19489,30 +19534,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19520,30 +19565,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19551,60 +19596,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19613,79 +19658,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19694,7 +19739,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19702,7 +19747,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19712,21 +19757,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19734,7 +19779,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19743,7 +19788,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19753,14 +19798,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19769,28 +19814,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19799,27 +19844,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19829,7 +19874,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19839,13 +19884,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20065,7 +20110,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20073,7 +20118,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20084,15 +20129,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20100,7 +20145,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20108,7 +20153,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20120,43 +20165,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20165,20 +20210,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20256,6 +20301,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/mk/LC_MESSAGES/messages.po b/locales/mk/LC_MESSAGES/messages.po index 8a174919a..5a1732564 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2023-10-21 04:04+0000\n" "Last-Translator: \"Kristijan \\\"Fremen\\\" Velkovski\" \n" "Language-Team: Macedonian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3179,13 +3178,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8659,7 +8659,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8859,45 +8859,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12175,7 +12205,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12184,11 +12214,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12310,15 +12340,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12417,16 +12447,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12617,94 +12647,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12712,7 +12723,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12722,33 +12733,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12756,50 +12767,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12807,64 +12818,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12872,13 +12883,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12886,36 +12897,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12924,13 +12943,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12938,20 +12957,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12959,7 +12978,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12969,11 +12988,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12981,7 +13000,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12991,18 +13010,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13011,7 +13030,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13022,63 +13041,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13089,33 +13133,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13124,89 +13168,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16116,7 +16160,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16368,24 +16412,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16393,14 +16438,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16408,7 +16453,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16416,24 +16461,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16441,7 +16486,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16452,17 +16497,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16470,19 +16515,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16491,20 +16536,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16512,18 +16557,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16531,7 +16576,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16539,14 +16584,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18582,7 +18627,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18915,29 +18960,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18945,48 +18990,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18994,7 +19039,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19002,11 +19047,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19014,11 +19059,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19026,20 +19071,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19048,13 +19093,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19064,28 +19109,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19096,18 +19141,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19115,22 +19160,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19139,11 +19184,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19153,11 +19198,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19167,11 +19212,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19179,11 +19224,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19194,11 +19239,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19206,11 +19251,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19218,11 +19263,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19232,11 +19277,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19244,11 +19289,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19256,11 +19301,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19268,11 +19313,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19281,11 +19326,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19294,11 +19339,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19308,7 +19353,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19316,69 +19361,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19386,48 +19431,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19438,7 +19483,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19448,17 +19493,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19467,14 +19512,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19485,7 +19530,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19493,30 +19538,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19524,30 +19569,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19555,60 +19600,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19617,79 +19662,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19698,7 +19743,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19706,7 +19751,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19716,21 +19761,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19738,7 +19783,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19747,7 +19792,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19757,14 +19802,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19773,28 +19818,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19803,27 +19848,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19833,7 +19878,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19843,13 +19888,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20069,7 +20114,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20077,7 +20122,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20088,15 +20133,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20104,7 +20149,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20112,7 +20157,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20124,43 +20169,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20169,20 +20214,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20260,6 +20305,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/pl/LC_MESSAGES/messages.po b/locales/pl/LC_MESSAGES/messages.po index 15db6ede0..bbef123ca 100644 --- a/locales/pl/LC_MESSAGES/messages.po +++ b/locales/pl/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/pt_BR/LC_MESSAGES/messages.po b/locales/pt_BR/LC_MESSAGES/messages.po index 7fb3d3a5f..bcd13d0c4 100644 --- a/locales/pt_BR/LC_MESSAGES/messages.po +++ b/locales/pt_BR/LC_MESSAGES/messages.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-07-30 13:48+0000\n" "Last-Translator: Alefsander Ribeiro Nascimento \n" "Language-Team: Portuguese (Brazil) `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." @@ -2903,7 +2902,7 @@ msgstr "" "Mais alguns exemplos de números de versão incomuns são fornecidos em uma " "`postagem no blog `_ de Seth Larson." -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_, `de Brett Cannon `_. Para uma visão " "humorística, leia sobre ZeroVer_." -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -4162,13 +4161,14 @@ msgstr "Coluna" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Descrição" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Exemplos" @@ -11484,7 +11484,7 @@ msgid "Dependencies and requirements" msgstr "Dependências e requisitos" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "``dependencies``/``optional-dependencies``" @@ -11739,13 +11739,13 @@ msgstr "" "especial ``'Private :: Do Not Upload'``. PyPI sempre rejeitará pacotes com " "classificadores começando com ``\"Private ::'``." -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "``urls``" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." @@ -11753,21 +11753,56 @@ msgstr "" "Uma lista de URLs associadas ao seu projeto, exibida na barra lateral " "esquerda da página do projeto PyPI." -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +#, fuzzy +#| msgid "" +#| "Note that if the key contains spaces, it needs to be quoted, e.g., " +#| "``Website = \"https://example.com\"`` but ``\"Official Website\" = " +#| "\"https://example.com\"``." msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." msgstr "" "Note que se a chave contém espaços, ela precisa ser citada, por exemplo, " "``Website = \"https://example.com\"``, mas ``\"Official Website\" = " "\"https://example.com\"``." -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "Plugins avançados" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " @@ -11777,15 +11812,15 @@ msgstr "" "Pytest_ e Pygments_. Para criar tal plugin, você precisa declará-lo em uma " "subtabela de ``[project.entry-points]`` assim:" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "Veja o :ref:`guia Plugin ` para mais informações." -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "Um exemplo completo" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -16138,7 +16173,7 @@ msgstr "" "com um pacote totalmente instalado antes de aceitá-lo como um bug genuíno." #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -16147,11 +16182,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "Histórico" @@ -16316,15 +16351,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "Exemplo::" @@ -16453,16 +16488,16 @@ msgstr "" "de \"Operating System\". Veja \"Classifier\" abaixo." #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "Exemplos::" @@ -16721,32 +16756,10 @@ msgstr "" "a especificação para corresponder ao padrão de fato." #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "Home-page" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "Uma string contendo a URL para a página da distribuição." - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "Download-URL" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" -"Uma string contendo a URL a partir da qual esta versão da distribuição pode " -"ser baixada. (Isso significa que a URL não pode ser algo como \".../" -"BeagleVote-latest.tgz\", mas deve ser \".../BeagleVote-0.45.tgz\".)" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "Author" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." @@ -16754,11 +16767,11 @@ msgstr "" "Um string contendo o nome do autor, no mínimo; informações de contato " "adicionais podem ser fornecidas." -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "Author-email" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." @@ -16766,8 +16779,8 @@ msgstr "" "Uma string contendo o endereço de e-mail do autor. Ela pode conter um nome e " "endereço de e-mail nas formas válidos para um cabeçalho ``From:`` do RFC-822." -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" @@ -16775,11 +16788,11 @@ msgstr "" "De acordo com RFC-822, este campo pode conter vários endereços de e-mail " "separados por vírgula::" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Mantenedor" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." @@ -16787,7 +16800,7 @@ msgstr "" "Uma string contendo o nome do mantenedor, no mínimo; informações de contato " "adicionais podem ser fornecidas." -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " @@ -16797,11 +16810,11 @@ msgstr "" "por alguém que não seja o autor original: ele deve ser omitido se for " "idêntico a ``Author``." -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "Maintainer-email" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." @@ -16810,7 +16823,7 @@ msgstr "" "nome e endereço de e-mail nas formas válidas para um cabeçalho ``From:`` do " "RFC-822." -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " @@ -16820,17 +16833,17 @@ msgstr "" "por alguém que não seja o autor original: ele deve ser omitido se for " "idêntico a ``Author-email``." -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "License" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 #, fuzzy #| msgid "in favour of ``Requires-Dist``" msgid "in favour of ``License-Expression``." msgstr "em favor de ``Requires-Dist``" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -16838,7 +16851,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -16853,35 +16866,35 @@ msgstr "" "especificar uma versão particular de uma licença que é nomeada através do " "campo ``Classifier``, ou para indicar uma variação ou exceção a tal licença." -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 #, fuzzy #| msgid "Requires-Dist (multiple use)" msgid "License-File (multiple use)" msgstr "Requires-Dist (vários usos)" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "Classifier (vários usos)" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -16893,30 +16906,30 @@ msgstr "" "Package Index publica uma lista dinâmica de `classificadores atualmente " "definidos `__." -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" "Este campo pode ser seguido por um marcador de ambiente após um ponto e " "vírgula." -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "Requires-Dist (vários usos)" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." @@ -16924,7 +16937,7 @@ msgstr "" "A especificação do formato de campo foi relaxada para aceitar a sintaxe " "usada por ferramentas de publicação populares." -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." @@ -16932,11 +16945,11 @@ msgstr "" "Cada entrada contém uma string nomeando algum outro projeto distutils " "requerido por esta distribuição." -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "O formato de uma string de requisito contém de uma a quatro partes:" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." @@ -16944,7 +16957,7 @@ msgstr "" "Um nome de projeto, no mesmo formato do campo ``Name:``. A única parte " "obrigatória." -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -16956,7 +16969,7 @@ msgstr "" "precisar de dependências extras. Os nomes DEVEM estar em conformidade com as " "restrições especificadas pelo campo ``Provides-Extra:``." -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." @@ -16965,7 +16978,7 @@ msgstr "" "aceitar parênteses opcionais em torno disso, mas as ferramentas que o geram " "não devem usar parênteses." -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." @@ -16973,11 +16986,11 @@ msgstr "" "Um marcador de ambiente após um ponto e vírgula. Isso significa que o " "requisito só é necessário nas condições especificadas." -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "Veja a :pep:`508` para detalhes completos do formato permitido." -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." @@ -16985,7 +16998,7 @@ msgstr "" "Os nomes dos projetos devem corresponder aos nomes encontrados no `Python " "Package Index`_." -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." @@ -16993,11 +17006,11 @@ msgstr "" "Os especificadores de versão devem seguir as regras descritas em :doc:" "`version-specifiers`." -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "Requires-Python" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " @@ -17007,12 +17020,12 @@ msgstr "" "é compatível. As ferramentas de instalação podem observar isso ao escolher " "qual versão de um projeto instalar." -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" "O valor deve estar no formato especificado em :doc:`version-specifiers`." -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 #, fuzzy msgid "" "For example, if a distribution uses :ref:`f-strings ` " @@ -17021,15 +17034,15 @@ msgstr "" "Por exemplo, se uma distribuição usa :ref:`f-strings ` " "então pode impedir a instalação em Python < 3.6 especificando::" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "Este campo não pode ser seguido por um marcador de ambiente." -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "Requires-External (vários usos)" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -17041,7 +17054,7 @@ msgstr "" "uma dica para os mantenedores do projeto downstream, e não tem semântica que " "seja significativa para a distribuição ``distutils``." -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." @@ -17049,7 +17062,7 @@ msgstr "" "O formato de uma string de requisito é o nome de uma dependência externa, " "opcionalmente seguido por uma declaração de versão entre parênteses." -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -17062,16 +17075,16 @@ msgstr "" "`: eles devem corresponder ao esquema de versão usado " "pela dependência externa." -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" "Observe que não há uma regra específica sobre as strings a serem usadas." -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "Project-URL (vários usos)" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." @@ -17079,15 +17092,23 @@ msgstr "" "Uma string contendo uma URL navegável para o projeto e um rótulo para ele, " "separados por uma vírgula." -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "O rótulo é um texto livre limitado a 32 caracteres." -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "Provides-Extra (vários usos)" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " @@ -17098,7 +17119,7 @@ msgstr "" "restrições de valor foram alinhadas com ``Name:`` e as regras de " "normalização foram introduzidas." -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -17112,7 +17133,7 @@ msgstr "" "hífen. Os nomes são limitados àqueles que correspondem ao seguinte regex " "(que elimina ambiguidade)::" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." @@ -17120,7 +17141,7 @@ msgstr "" "O nome especificado pode ser usado para tornar uma dependência condicional " "ao fato de o recurso opcional ter sido solicitado." -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -17132,7 +17153,7 @@ msgstr "" "(,). Os requisitos são avaliados para cada recurso solicitado e adicionados " "ao conjunto de requisitos para a distribuição." -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " @@ -17142,7 +17163,7 @@ msgstr "" "dependências que são necessárias para executar testes automatizados e gerar " "documentação, respectivamente." -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." @@ -17150,7 +17171,7 @@ msgstr "" "É válido especificar ``Provides-Extra:`` sem referenciá-lo em qualquer " "``Requer-Dist:``." -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -17162,7 +17183,7 @@ msgstr "" "realizar comparações. Ferramentas que escrevem metadados DEVEM gerar um erro " "se duas entradas ``Provides-Extra:`` colidirem após serem normalizadas." -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -17179,11 +17200,11 @@ msgstr "" "optar por gerar um erro ao ler um nome inválido para versões de metadados " "mais antigas." -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "Campos raramente usados" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -17195,7 +17216,7 @@ msgstr "" "Linux, e não está claro como as ferramentas devem interpretá-los no contexto " "de um servidor de indexação aberto, como `PyPI `__." -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -17211,11 +17232,11 @@ msgstr "" "informativos e também podem ser usados para o propósito originalmente " "pretendido em combinação com um repositório de pacotes com curadoria." -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "Provides-Dist (vários usos)" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " @@ -17225,7 +17246,7 @@ msgstr "" "contido nesta distribuição. Este campo *deve* incluir o projeto identificado " "no campo ``Name``, seguido da versão: Nome (Versão)." -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -17240,7 +17261,7 @@ msgstr "" "Instalar tal distribuição de código-fonte satisfaz os requisitos para " "``ZODB`` e ``transaction``." -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -17258,7 +17279,7 @@ msgstr "" "declarar que fornece ``ORM-bindings``, permitindo que outros projetos " "dependam apenas de ter no máximo um deles instalado." -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " @@ -17268,11 +17289,11 @@ msgstr "" "descritas em :doc:`version-specifiers`. O número da versão da distribuição " "estará implícito se nenhum for especificado." -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "Obsoletes-Dist (vários usos)" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " @@ -17282,7 +17303,7 @@ msgstr "" "distutils que esta distribuição torna obsoleta, o que significa que os dois " "projetos não devem ser instalados ao mesmo tempo." -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." @@ -17290,7 +17311,7 @@ msgstr "" "Declarações de versão podem ser fornecidas. Os números de versão devem estar " "no formato especificado em :doc:`version-specifiers`." -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " @@ -17300,19 +17321,53 @@ msgstr "" "projeto, por exemplo, Gorgon 2.3 é incluído no Torqued Python 1.0. Quando " "você instala o Torqued Python, a distribuição Gorgon deve ser removida." -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "Campos descontinuados" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "Home-page" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "Uma string contendo a URL para a página da distribuição." + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "Download-URL" + +#: ../source/specifications/core-metadata.rst:829 +#, fuzzy +#| msgid "" +#| "A string containing the URL from which this version of the distribution " +#| "can be downloaded. (This means that the URL can't be something like " +#| "\".../BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45." +#| "tgz\".)" +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" +"Uma string contendo a URL a partir da qual esta versão da distribuição pode " +"ser baixada. (Isso significa que a URL não pode ser algo como \".../" +"BeagleVote-latest.tgz\", mas deve ser \".../BeagleVote-0.45.tgz\".)" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "Requires" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "em favor de ``Requires-Dist``" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." @@ -17320,7 +17375,7 @@ msgstr "" "Cada entrada contém uma string descrevendo algum outro módulo ou pacote " "requerido por este pacote." -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " @@ -17330,7 +17385,7 @@ msgstr "" "pacote utilizável com a instrução ``import``, opcionalmente seguida por uma " "declaração de versão dentro de parênteses." -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -17348,7 +17403,7 @@ msgstr "" "release\" opcional no final que consiste na letra 'a' ou 'b' seguida de um " "número. Os números da versão do exemplo são \"1.0\", \"2.3a2\", \"1.3.99\"." -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." @@ -17356,7 +17411,7 @@ msgstr "" "Qualquer número de operadores condicionais pode ser especificado, por " "exemplo, a string \">1.0, !=1.3.4, <2.0\" é uma declaração de versão válida." -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." @@ -17364,7 +17419,7 @@ msgstr "" "Todos os seguintes são possíveis strings de requisito: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." @@ -17372,15 +17427,15 @@ msgstr "" "Não há nenhuma lista canônica de quais strings devem ser usadas; a " "comunidade Python é livre para escolher seus próprios padrões." -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "Provides" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "em favor de ``Provides-Dist``" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -17394,15 +17449,15 @@ msgstr "" "pode ser fornecida (sem um operador de comparação); o número de versão do " "pacote será implícito se nenhum for especificado." -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "Obsoletes" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "em favor de ``Obsoletes-Dist``" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " @@ -17412,7 +17467,7 @@ msgstr "" "pacote torna obsoleta, o que significa que os dois projetos não devem ser " "instalados ao mesmo tempo. Declarações de versão pode ser fornecidas." -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " @@ -17422,74 +17477,74 @@ msgstr "" "projeto, por exemplo, Gorgon 2.3 é incluído no Torqued Python 1.0. Quando " "você instala o Torqued Python, o pacote Gorgon deve ser removido." -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 #, fuzzy msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" "Adicionada documentação para o campo ``Description-Content-Type``. (:pr:" "`258`)" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "Adicionado o campo ``Dinâmico``." -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 #, fuzzy #| msgid "Added the ``Dynamic`` field." msgid "Added the ``License-Expression`` field." msgstr "Adicionado o campo ``Dinâmico``." -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 #, fuzzy #| msgid "Added the ``Dynamic`` field." msgid "Added the ``License-File`` field." msgstr "Adicionado o campo ``Dinâmico``." -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "Marcação reStructuredText: https://docutils.sourceforge.io/" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" @@ -20966,7 +21021,7 @@ msgid "``dependencies``" msgstr "``dependencies``" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "``dynamic``" @@ -21302,15 +21357,15 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -"Uma tabela de URLs onde a chave é o rótulo da URL e o valor é a URL em si." -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "Pontos de entrada" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" @@ -21318,11 +21373,11 @@ msgstr "" "Tipo TOML_: tabela (``[project.scripts]``, ``[project.gui-scripts]`` e " "``[project.entry-points]``)" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr ":ref:`Especificação de pontos de entrada `" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -21334,7 +21389,7 @@ msgstr "" "de pontos de entrada `. A chave da tabela é o nome do ponto de " "entrada e o valor é a referência do objeto." -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " @@ -21344,7 +21399,7 @@ msgstr "" "ref:`especificação de pontos de entrada `. Seu formato é o " "mesmo que ``[project.scripts]``." -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -21357,7 +21412,7 @@ msgstr "" "aninhadas, mas sim manter os grupos de pontos de entrada em apenas um nível " "de profundidade." -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -21369,7 +21424,7 @@ msgstr "" "gui_scripts]``, pois elas seriam ambíguas perante ``[project.scripts]`` e " "``[project.gui-scripts]``, respectivamente." -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" @@ -21377,7 +21432,7 @@ msgstr "" "Tipo TOML_: Vetor de strings da :pep:`508` (``dependencies``) e uma tabela " "com valores de vetores de strings da :pep:`508` (``optional-dependencies``)" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra ` e :ref:`Provides-Extra `" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "As dependências (opcionais) do projeto." -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -21403,7 +21458,7 @@ msgstr "" "string válida :pep:`508`. Cada string mapeia diretamente para um :ref:" "`Requires-Dist `." -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -21421,11 +21476,11 @@ msgstr "" "requires-dist>` para os metadados correspondentes de :ref:`Provides-Extra " "`." -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "Tipo TOML_: vetor de string" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" @@ -21433,7 +21488,7 @@ msgstr "" "Campo correspondente dos :ref:`metadados principais `: :ref:" "`Dynamic `" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -21446,7 +21501,7 @@ msgstr "" "não especificados e espera-se que permaneçam não especificados em comparação " "a serem fornecidos por meio de ferramentas posteriormente." -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." @@ -21455,7 +21510,7 @@ msgstr "" "estaticamente (o que significa que os metadados não listam a chave em " "``dynamic``)." -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." @@ -21463,7 +21518,7 @@ msgstr "" "Um backend de construção DEVE gerar um erro se os metadados especificarem " "``name`` em ``dynamic``." -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -21477,7 +21532,7 @@ msgstr "" "um erro, caso contrário , ou seja, não deve ser possível que uma chave " "obrigatória não seja listada de alguma forma na tabela ``[project]``)." -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " @@ -21488,7 +21543,7 @@ msgstr "" "expectativa for um backend de construção fornecerá os dados para a chave " "mais tarde." -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." @@ -21496,7 +21551,7 @@ msgstr "" "Os backends de construção DEVEM levantar um erro se os metadados " "especificarem uma chave estaticamente, além de serem listados em ``dynamic``." -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -21508,7 +21563,7 @@ msgstr "" "(ou seja, ``dynamic`` é a única maneira de permitir que uma ferramenta " "preencha metadados e o usuário deve optar pelo preenchimento)." -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " @@ -21519,11 +21574,11 @@ msgstr "" "capaz de determinar os dados para ele (omitir os dados, se determinado como " "o valor exato, é aceitável) ." -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -21531,7 +21586,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -21539,14 +21594,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -23768,7 +23823,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "Especificadores de versão" @@ -24106,30 +24161,30 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 #, fuzzy msgid "Pre-releases" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -24137,49 +24192,49 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 #, fuzzy msgid "Post-releases" msgstr "zest.releaser" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -24187,7 +24242,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -24195,11 +24250,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "Pós lançamentos também são permitidos para pré-lançamentos::" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -24207,11 +24262,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "Versões de desenvolvimento" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -24219,20 +24274,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -24241,13 +24296,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -24257,29 +24312,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Versões" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -24290,18 +24345,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "Normalização" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -24309,23 +24364,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "Sensível a maiúsculas e minúsculas" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Normalização" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -24334,12 +24389,12 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 #, fuzzy msgid "Pre-release separators" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -24349,12 +24404,12 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 #, fuzzy msgid "Pre-release spelling" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -24364,11 +24419,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "Número de pré-lançamento implícito" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -24376,11 +24431,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "Separadores de pós lançamento" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -24391,12 +24446,12 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 #, fuzzy msgid "Post release spelling" msgstr "Versionamento de pré-lançamento" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -24404,11 +24459,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "Número implícito de pós lançamento" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -24416,11 +24471,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "Pós lançamentos implícitos" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -24430,11 +24485,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "Separadores de versões de desenvolvimento" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -24442,11 +24497,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "Número implícito de versão de desenvolvimento" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -24454,12 +24509,12 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 #, fuzzy msgid "Local version segments" msgstr "Identificadores de versão local" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -24467,11 +24522,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "Caractere predecessor v" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -24480,11 +24535,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -24493,12 +24548,12 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 #, 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:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -24508,7 +24563,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -24516,70 +24571,70 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 #, fuzzy msgid "Simple \"major.minor\" versioning::" msgstr "Versionamento serial" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "Versionamento simples \"major.minor.micro\" ::" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -24587,48 +24642,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "Ordenação de versões em diferentes versões de metadados" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -24639,7 +24694,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -24649,18 +24704,18 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 #, fuzzy msgid "Compatibility with other version schemes" msgstr "Lidando com os wheels universais" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -24669,14 +24724,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -24687,7 +24742,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -24695,31 +24750,31 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 #, fuzzy msgid "DVCS based version labels" msgstr "Versionamento baseado em data" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -24727,31 +24782,31 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 #, fuzzy msgid "Olson database versioning" msgstr "Versionamento baseado em data" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -24759,60 +24814,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: `Compatible release`_ clause" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "``==``: `Version matching`_ clause" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: `Version exclusion`_ clause" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "``<``, ``>``: `Exclusive ordered comparison`_ clause" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: `Arbitrary equality`_ clause." -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -24821,81 +24876,81 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "Versão compatível" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 #, 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:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 #, fuzzy msgid "Version matching" msgstr "Versão" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -24904,7 +24959,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -24912,7 +24967,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -24922,21 +24977,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -24944,7 +24999,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -24953,7 +25008,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -24963,14 +25018,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -24979,29 +25034,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "Especificador de Versão" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "Comparação ordenada inclusiva" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -25010,27 +25065,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "Comparação ordenada exclusiva" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -25040,7 +25095,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -25050,13 +25105,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -25285,7 +25340,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -25293,7 +25348,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -25304,17 +25359,17 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 #, fuzzy msgid "Remote URL examples::" msgstr "Por exemplo::" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 #, fuzzy msgid "File URLs" msgstr "URLs de arquivos" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -25322,7 +25377,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -25330,7 +25385,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -25342,43 +25397,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 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:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -25387,20 +25442,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -25481,6 +25536,333 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +msgid "Well-known Project URLs in Metadata" +msgstr "Nome do projeto" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +#, fuzzy +#| msgid "" +#| "This document describes the dependency specifiers format as originally " +#| "specified in :pep:`508`." +msgid "This specification was originally defined in :pep:`753`." +msgstr "" +"Este documento descreve o formato dos especificadores de dependência " +"conforme originalmente especificado na :pep:`508`." + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Normalização" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "Nomes não normalizados válidos" + +#: ../source/specifications/well-known-project-urls.rst:76 +#, fuzzy +#| msgid "Home-page" +msgid "``Homepage``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +#, fuzzy +#| msgid "Home-page" +msgid "``homepage``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:78 +#, fuzzy +#| msgid "Home-page" +msgid "``Home-page``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:80 +#, fuzzy +#| msgid "Home page" +msgid "``Home page``" +msgstr "Site" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +#, fuzzy +msgid "``documentation`` (Documentation)" +msgstr "Criando documentação" + +#: ../source/specifications/well-known-project-urls.rst:124 +#, fuzzy +msgid "The project's online documentation" +msgstr "Criando documentação" + +#: ../source/specifications/well-known-project-urls.rst:125 +#, fuzzy +#| msgid "``upload_docs``" +msgid "``docs``" +msgstr "``upload_docs``" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +#| msgid "Basic information" +msgid "Funding Information" +msgstr "Informações básicas" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +#| msgid "Example" +msgid "Example behavior" +msgstr "Exemplo" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +#, fuzzy +#| msgid "Core metadata specifications" +msgid "Core metadata representation" +msgstr "Especificações de metadados principais" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "Como obter suporte" @@ -27231,6 +27613,12 @@ msgid "" "the file is empty)." msgstr "" +#~ msgid "" +#~ "A table of URLs where the key is the URL label and the value is the URL " +#~ "itself." +#~ msgstr "" +#~ "Uma tabela de URLs onde a chave é o rótulo da URL e o valor é a URL em si." + #~ msgid "Update this page for build backends other than setuptools." #~ msgstr "Atualizar esta página para construir backends além do setuptools." diff --git a/locales/ro/LC_MESSAGES/messages.po b/locales/ro/LC_MESSAGES/messages.po index 60623a429..d3f4b14bd 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2021-08-20 01:32+0000\n" "Last-Translator: GUILHERME FERNANDES NETO \n" "Language-Team: Romanian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3177,13 +3176,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8657,7 +8657,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8857,45 +8857,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12173,7 +12203,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12182,11 +12212,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12308,15 +12338,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12415,16 +12445,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12615,94 +12645,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12710,7 +12721,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12720,33 +12731,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12754,50 +12765,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12805,64 +12816,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12870,13 +12881,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12884,36 +12895,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12922,13 +12941,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12936,20 +12955,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12957,7 +12976,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12967,11 +12986,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12979,7 +12998,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12989,18 +13008,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13009,7 +13028,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13020,63 +13039,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13087,33 +13131,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13122,89 +13166,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16114,7 +16158,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16366,24 +16410,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16391,14 +16436,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16406,7 +16451,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16414,24 +16459,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16439,7 +16484,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16450,17 +16495,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16468,19 +16513,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16489,20 +16534,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16510,18 +16555,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16529,7 +16574,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16537,14 +16582,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18580,7 +18625,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18913,29 +18958,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18943,48 +18988,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18992,7 +19037,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19000,11 +19045,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19012,11 +19057,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19024,20 +19069,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19046,13 +19091,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19062,28 +19107,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19094,18 +19139,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19113,22 +19158,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19137,11 +19182,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19151,11 +19196,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19165,11 +19210,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19177,11 +19222,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19192,11 +19237,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19204,11 +19249,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19216,11 +19261,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19230,11 +19275,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19242,11 +19287,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19254,11 +19299,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19266,11 +19311,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19279,11 +19324,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19292,11 +19337,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19306,7 +19351,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19314,69 +19359,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19384,48 +19429,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19436,7 +19481,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19446,17 +19491,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19465,14 +19510,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19483,7 +19528,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19491,30 +19536,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19522,30 +19567,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19553,60 +19598,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19615,79 +19660,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19696,7 +19741,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19704,7 +19749,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19714,21 +19759,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19736,7 +19781,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19745,7 +19790,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19755,14 +19800,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19771,28 +19816,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19801,27 +19846,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19831,7 +19876,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19841,13 +19886,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20067,7 +20112,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20075,7 +20120,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20086,15 +20131,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20102,7 +20147,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20110,7 +20155,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20122,43 +20167,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20167,20 +20212,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20258,6 +20303,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/ru/LC_MESSAGES/messages.po b/locales/ru/LC_MESSAGES/messages.po index 8f3556eee..667b77a73 100644 --- a/locales/ru/LC_MESSAGES/messages.po +++ b/locales/ru/LC_MESSAGES/messages.po @@ -13,7 +13,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-07-15 14:09+0000\n" "Last-Translator: gfbdrgng \n" "Language-Team: Russian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." @@ -2889,7 +2888,7 @@ msgstr "" "Еще несколько примеров необычных номеров версий приведены в `блоговом посте " "<версии-Сет-Ларсон_>`_ Сета Ларсона." -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_, Бретт Кэннон `_. Для юмористического восприятия читайте о ZeroVer_." -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -4162,13 +4161,14 @@ msgstr "Колонка" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Описание" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Примеры" @@ -11573,7 +11573,7 @@ msgid "Dependencies and requirements" msgstr "Зависимости и требования" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "``зависимости``/``опциональные-зависимости``" @@ -11827,13 +11827,13 @@ msgstr "" "классификатор ``Private :: Do Not Upload``. PyPI всегда будет отклонять " "пакеты с классификаторами, начинающимися с ``Private ::``." -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "``urls``" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." @@ -11841,21 +11841,56 @@ msgstr "" "Список URL-адресов, связанных с вашим проектом, отображаемый на левой " "боковой панели страницы проекта PyPI." -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +#, fuzzy +#| msgid "" +#| "Note that if the key contains spaces, it needs to be quoted, e.g., " +#| "``Website = \"https://example.com\"`` but ``\"Official Website\" = " +#| "\"https://example.com\"``." msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." msgstr "" "Обратите внимание, что если ключ содержит пробелы, его необходимо заключить " "в кавычки, например, ``Website = \"https://example.com\"``, но " "``\"Официальный сайт\" = \"https://example.com\"``." -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "Расширенные плагины" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " @@ -11865,17 +11900,17 @@ msgstr "" "можно привести Pytest_ и Pygments_. Чтобы создать такой плагин, нужно " "объявить его в подтаблице ``[project.entry-points]`` следующим образом:" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" "Дополнительную информацию см. в :ref:`Руководство по плагинам `." -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "Полный пример" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -16221,7 +16256,7 @@ msgstr "" "установленным пакетом, прежде чем принять его за настоящую ошибку." #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -16230,11 +16265,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "История" @@ -16397,15 +16432,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "Пример::" @@ -16532,16 +16567,16 @@ msgstr "" "система\". См. раздел \"Классификатор\" ниже." #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "Примеры::" @@ -16800,33 +16835,10 @@ msgstr "" "она соответствовала стандарту де-факто." #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "Home-page" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "Строка, содержащая URL-адрес главной страницы дистрибутива." - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "Download-URL" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" -"Строка, содержащая URL, по которому можно загрузить данную версию " -"дистрибутива. (Это означает, что URL не может быть чем-то вроде \".../" -"BeagleVote-latest.tgz\", а вместо этого должен быть \".../BeagleVote-0.45." -"tgz\".)" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "Автор" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." @@ -16834,11 +16846,11 @@ msgstr "" "Строка, содержащая, как минимум, имя автора; может быть указана " "дополнительная контактная информация." -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "Author-email" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." @@ -16846,8 +16858,8 @@ msgstr "" "Строка, содержащая адрес электронной почты автора. Может содержать имя и " "адрес электронной почты в законных формах для заголовка RFC-822 ``From:``." -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" @@ -16855,11 +16867,11 @@ msgstr "" "Согласно RFC-822, это поле может содержать несколько адресов электронной " "почты, разделенных запятыми::" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Сопровождающий" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." @@ -16867,7 +16879,7 @@ msgstr "" "Строка, содержащая, как минимум, имя сопровождающего; может быть " "предоставлена дополнительная контактная информация." -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " @@ -16877,11 +16889,11 @@ msgstr "" "проект поддерживается кем-то, кроме оригинального автора: его следует " "опустить, если оно идентично ``Author``." -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "Maintainer-email" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." @@ -16890,7 +16902,7 @@ msgstr "" "имя и адрес электронной почты в законных формах для заголовка RFC-822 ``From:" "``." -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " @@ -16900,17 +16912,17 @@ msgstr "" "проект поддерживается кем-то, кроме оригинального автора: оно должно быть " "опущено, если оно идентично ``Author-email``." -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "Лицензия" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 #, fuzzy #| msgid "in favour of ``Requires-Dist``" msgid "in favour of ``License-Expression``." msgstr "в пользу ``Requires-Dist``" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -16918,7 +16930,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -16934,35 +16946,35 @@ msgstr "" "``Классификатор'', или для указания разновидности или исключения из такой " "лицензии." -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 #, fuzzy #| msgid "Requires-Dist (multiple use)" msgid "License-File (multiple use)" msgstr "Requires-Dist (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "Classifier (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -16974,28 +16986,28 @@ msgstr "" "Index публикует динамический список `определенных в данный момент " "классификаторов` `__." -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "За этим полем может следовать маркер окружения после точки с запятой." -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "Requires-Dist (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." @@ -17003,7 +17015,7 @@ msgstr "" "Спецификация формата полей была смягчена, чтобы принять синтаксис, " "используемый популярными издательскими инструментами." -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." @@ -17011,11 +17023,11 @@ msgstr "" "Каждая запись содержит строку с названием другого проекта distutils, " "необходимого для данного дистрибутива." -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "Формат строки требований содержит от одной до четырех частей:" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." @@ -17023,7 +17035,7 @@ msgstr "" "Название проекта в том же формате, что и поле ``Имя:``. Единственная " "обязательная часть." -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -17035,7 +17047,7 @@ msgstr "" "потребоваться дополнительные зависимости. Имена ДОЛЖНЫ соответствовать " "ограничениям, указанным в поле ``Provides-Extra:``." -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." @@ -17044,7 +17056,7 @@ msgstr "" "необязательные круглые скобки вокруг него, но инструменты, генерирующие его, " "не должны использовать круглые скобки." -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." @@ -17052,11 +17064,11 @@ msgstr "" "Маркер окружения после точки с запятой. Это означает, что требование " "необходимо только в указанных условиях." -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "Подробную информацию о допустимом формате см. в :pep:`508`." -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." @@ -17064,7 +17076,7 @@ msgstr "" "Имена проектов должны соответствовать именам, найденным в `Python Package " "Index`_." -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." @@ -17072,11 +17084,11 @@ msgstr "" "Спецификаторы версий должны следовать правилам, описанным в :doc:`version-" "specifiers`." -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "Requires-Python" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " @@ -17086,11 +17098,11 @@ msgstr "" "дистрибутив. Утилиты установки могут учитывать это поле при выборе версии " "проекта для установки." -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "Значение должно быть в формате, указанном в :doc:`version-specifiers`." -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" @@ -17098,15 +17110,15 @@ msgstr "" "Например, если дистрибутив использует :ref:`f-strings `, " "то он может предотвратить установку на Python < 3.6, указав::" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "За этим полем не может следовать маркер окружения." -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "Requires-External (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -17118,7 +17130,7 @@ msgstr "" "сопровождающих проектов и не имеет семантики, значимой для дистрибутива " "``distutils``." -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." @@ -17126,7 +17138,7 @@ msgstr "" "Формат строки требований - это имя внешней зависимости, за которым в круглых " "скобках по желанию следует объявление версии." -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -17138,17 +17150,17 @@ msgstr "" "указанному в :ref:`Спецификация спецификатора версии `: " "они должны соответствовать схеме версий, используемой внешней зависимостью." -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" "Обратите внимание, что нет никаких особых правил относительно используемых " "строк." -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "Project-URL (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." @@ -17156,16 +17168,24 @@ msgstr "" "Строка, содержащая просматриваемый URL-адрес проекта и его метку, " "разделенные запятой." -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" "Этикетка представляет собой свободный текст, ограниченный 32 символами." -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "Provides-Extra (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " @@ -17176,7 +17196,7 @@ msgstr "" "ограничения на значения были приведены в соответствие с ``Name:`` и были " "введены правила нормализации." -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -17190,7 +17210,7 @@ msgstr "" "Имена ограничиваются теми, которые соответствуют следующему регексу (который " "гарантирует однозначность)::" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." @@ -17198,7 +17218,7 @@ msgstr "" "Указанное имя можно использовать, чтобы сделать зависимость зависимой от " "того, была ли запрошена необязательная функция." -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -17210,7 +17230,7 @@ msgstr "" "(,). Требования оцениваются для каждой запрошенной функции и добавляются к " "набору требований для дистрибутива." -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " @@ -17220,7 +17240,7 @@ msgstr "" "зависимостей, необходимых для выполнения автоматизированных тестов и " "создания документации, соответственно." -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." @@ -17228,7 +17248,7 @@ msgstr "" "Разрешается указывать ``Provides-Extra:`` без ссылки на него в каком-либо " "``Requires-Dist:``." -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -17240,7 +17260,7 @@ msgstr "" "при выполнении сравнений. Средства записи метаданных ДОЛЖНЫ выдавать ошибку, " "если две записи ``Provides-Extra:`` будут конфликтовать после нормализации." -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -17257,11 +17277,11 @@ msgstr "" "Инструментальные средства МОГУТ выдавать ошибку при чтении недопустимого " "имени для старых версий метаданных." -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "Редко используемые поля" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -17274,7 +17294,7 @@ msgstr "" "интерпретировать их в контексте открытого индексного сервера, такого как " "`PyPI `__." -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -17290,11 +17310,11 @@ msgstr "" "использованы по своему первоначальному назначению в сочетании с курируемым " "репозиторием пакетов." -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "Provides-Dist (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " @@ -17304,7 +17324,7 @@ msgstr "" "содержится в этом дистрибутиве. Это поле *должно* включать проект, " "указанный в поле ``Имя``, за которым следует версия : Имя (Версия)." -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -17319,7 +17339,7 @@ msgstr "" "исходного дистрибутива удовлетворяет требованиям как для ``ZODB``, так и для " "``transaction``." -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -17338,7 +17358,7 @@ msgstr "" "позволяя другим проектам зависеть только от наличия хотя бы одной из этих " "привязок." -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " @@ -17348,11 +17368,11 @@ msgstr "" "правилам, описанным в :doc:`version-specifiers`. Номер версии дистрибутива " "будет подразумеваться, если он не указан." -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "Obsoletes-Dist (можно использовать несколько раз)" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " @@ -17362,7 +17382,7 @@ msgstr "" "который этот дистрибутив делает устаревшим, что означает, что эти два " "проекта не должны быть установлены одновременно." -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." @@ -17370,7 +17390,7 @@ msgstr "" "Декларации версий могут быть предоставлены. Номера версий должны быть в " "формате, указанном в :doc:`version-specifiers`." -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " @@ -17380,19 +17400,54 @@ msgstr "" "например, когда Gorgon 2.3 переходит в Torqued Python 1.0. При установке " "Torqued Python дистрибутив Gorgon должен быть удален." -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "Утраченные поля" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "Home-page" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "Строка, содержащая URL-адрес главной страницы дистрибутива." + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "Download-URL" + +#: ../source/specifications/core-metadata.rst:829 +#, fuzzy +#| msgid "" +#| "A string containing the URL from which this version of the distribution " +#| "can be downloaded. (This means that the URL can't be something like " +#| "\".../BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45." +#| "tgz\".)" +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" +"Строка, содержащая URL, по которому можно загрузить данную версию " +"дистрибутива. (Это означает, что URL не может быть чем-то вроде \".../" +"BeagleVote-latest.tgz\", а вместо этого должен быть \".../BeagleVote-0.45." +"tgz\".)" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "Требуется" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "в пользу ``Requires-Dist``" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." @@ -17400,7 +17455,7 @@ msgstr "" "Каждая запись содержит строку, описывающую другой модуль или пакет, " "необходимый для данного пакета." -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " @@ -17410,7 +17465,7 @@ msgstr "" "используемого с помощью оператора ``импорта``, за которым в круглых скобках " "по желанию следует объявление версии." -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -17428,7 +17483,7 @@ msgstr "" "конце, состоящим из буквы 'a' или 'b', за которой следует число. Примеры " "номеров версий: \"1.0\", \"2.3a2\", \"1.3.99\"," -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." @@ -17436,7 +17491,7 @@ msgstr "" "Можно указать любое количество условных операторов, например, строка " "\">1.0, !=1.3.4, <2.0\" является законным объявлением версии." -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." @@ -17444,7 +17499,7 @@ msgstr "" "Возможными строками требований являются все следующие: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." @@ -17452,15 +17507,15 @@ msgstr "" "Не существует канонического списка того, какие строки должны использоваться; " "сообщество Python оставляет за собой право выбирать собственные стандарты." -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "Предоставляет" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "в пользу ``Provides-Dist``" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -17474,15 +17529,15 @@ msgstr "" "версии (без оператора сравнения); номер версии пакета будет подразумеваться, " "если он не указан." -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "Обзоры" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "в пользу ``Obsoletes-Dist``" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " @@ -17492,7 +17547,7 @@ msgstr "" "пакет делает устаревшим, что означает, что эти два пакета не должны быть " "установлены одновременно. Могут быть предоставлены объявления версий." -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " @@ -17502,73 +17557,73 @@ msgstr "" "например, Gorgon 2.3 переходит в Torqued Python 1.0. При установке Torqued " "Python пакет Gorgon должен быть удален." -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "Март 2001: Core metadata 1.0 был одобрен через :pep:`241`." -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "Апрель 2003 года: Core metadata 1.1 был одобрен через :pep:`314`:" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "Февраль 2010 г: Core metadata 1.2 был одобрен через :pep:`345`." -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "Февраль 2018 г: Core metadata 2.1 был одобрен через :pep:`566`." -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "Добавлены ``Description-Content-Type`` и ``Provides-Extra``." -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "Добавлен метод canonical для преобразования метаданных в JSON." -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "Ограничение грамматики поля ``Имя``." -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "Октябрь 2020 года: Core metadata 2.2 был одобрен через :pep:`643`." -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "Добавлено поле ``Динамика``." -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "Март 2022: Core metadata 2.3 был одобрен через :pep:`685`." -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "Ограниченные дополнительные имена, подлежащие нормализации." -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 #, fuzzy #| msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "Октябрь 2020 года: Core metadata 2.2 был одобрен через :pep:`643`." -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 #, fuzzy #| msgid "Added the ``Dynamic`` field." msgid "Added the ``License-Expression`` field." msgstr "Добавлено поле ``Динамика``." -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 #, fuzzy #| msgid "Added the ``Dynamic`` field." msgid "Added the ``License-File`` field." msgstr "Добавлено поле ``Динамика``." -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "Разметка reStructuredText: https://docutils.sourceforge.io/" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "Длинные поля заголовка RFC 822: :rfc:`822#section-3.1.1`" @@ -21519,7 +21574,7 @@ msgid "``dependencies``" msgstr "``зависимости``" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "``динамический``" @@ -21855,15 +21910,15 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -"Таблица URL-адресов, где ключом является метка URL, а значением - сам URL." -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "Точки входа" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" @@ -21871,11 +21926,11 @@ msgstr "" "Тип TOML_: таблица (``[project.scripts]``, ``[project.gui-scripts]``, и " "``[project.entry-points]``)" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr ":ref:`Спецификация точек входа `" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -21887,7 +21942,7 @@ msgstr "" "точек входа `. Ключом таблицы является имя точки входа, а " "значением - ссылка на объект." -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " @@ -21897,7 +21952,7 @@ msgstr "" "спецификации точек входа `. Ее формат такой же, как и у " "``[project.scripts]``." -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -21910,7 +21965,7 @@ msgstr "" "создавать вложенные подтаблицы, а должны ограничиваться группами точек входа " "только одного уровня." -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -21922,7 +21977,7 @@ msgstr "" "entry-points.gui_scripts]``, поскольку они будут неоднозначными перед лицом " "``[project.scripts]`` и ``[project.gui-scripts]``, соответственно." -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" @@ -21930,7 +21985,7 @@ msgstr "" "Тип TOML_: Массив строк :pep:`508` (``зависимости``), и таблица со " "значениями массивов строк :pep:`508` (``опциональные-зависимости``)" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra ` и :ref:`Provides-Extra `" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "Зависимости проекта (необязательно)." -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -21956,7 +22011,7 @@ msgstr "" "как корректная строка :pep:`508`. Каждая строка сопоставляется " "непосредственно с записью :ref:`Requires-Dist `." -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -21975,11 +22030,11 @@ msgstr "" "для соответствующего метаданного :ref:`Provides-Extra `." -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "Тип TOML_: массив строк" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" @@ -21987,7 +22042,7 @@ msgstr "" "Соответствующее поле :ref:`core metadata `: :ref:`Dynamic " "`" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -22000,7 +22055,7 @@ msgstr "" "определены и, как ожидается, останутся неопределенными по сравнению с тем, " "что будет предоставлено с помощью инструментов позже." -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." @@ -22008,7 +22063,7 @@ msgstr "" "Бэкэнд сборки ДОЛЖЕН почитать статически заданные метаданные (это означает, " "что в метаданных не указан ключ в ``динамическом``)." -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." @@ -22016,7 +22071,7 @@ msgstr "" "Внутренний модуль сборки ДОЛЖЕН выдать ошибку, если в метаданных указано " "``имя`` в ``dynamic``." -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -22030,7 +22085,7 @@ msgstr "" "случае, т.е. не должно быть возможности, чтобы требуемый ключ не был как-то " "указан в таблице ``[project]``)." -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " @@ -22040,7 +22095,7 @@ msgstr "" "\"Optional\", метаданные МОГУТ указывать его в ``dynamic``, если " "предполагается, что сборка бэкенда предоставит данные для ключа позже." -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." @@ -22048,7 +22103,7 @@ msgstr "" "Внутренние компоненты сборки ДОЛЖНЫ выдать ошибку, если метаданные указывают " "ключ статически, а также перечислены в ``динамических``." -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -22060,7 +22115,7 @@ msgstr "" "это единственный способ позволить инструменту заполнить метаданные, и " "пользователь должен согласиться на заполнение)." -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " @@ -22070,11 +22125,11 @@ msgstr "" "``dynamic``, но бэкэнд сборки не смог определить данные для него (опускание " "данных, если определено, что это точное значение, допустимо)." -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "Произвольная конфигурация инструментов: таблица ``[tool]``" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -22087,7 +22142,7 @@ msgstr "" "``[tool]``, например, инструмент `flit `_ " "будет хранить свою конфигурацию в ``[tool.flit]``." -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -22100,7 +22155,7 @@ msgstr "" "может использовать подтаблицу ``tool.$NAME`` тогда и только тогда, когда он " "владеет записью для ``$NAME`` в Cheeseshop/PyPI." -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " @@ -22110,7 +22165,7 @@ msgstr "" "только ``[build-system]``, содержащую ключ ``requires`` и таблицу " "``[tool]``, была одобрена через :pep:`518``." -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -25016,7 +25071,7 @@ msgstr "" "стандартизированы с помощью :pep:`721`." #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "Спецификаторы версии" @@ -25486,11 +25541,11 @@ msgstr "" "Также допускаются сегменты релизов, основанные на дате. Пример схемы релиза " "на основе даты с использованием года и месяца релиза::" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "Предварительные выпуски" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." @@ -25499,7 +25554,7 @@ msgstr "" "кандидат\" для поддержки тестирования пользователями перед выпуском " "финального релиза." -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" @@ -25508,7 +25563,7 @@ msgstr "" "проекта, они обозначаются включением сегмента pre-release в идентификатор " "версии::" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." @@ -25516,7 +25571,7 @@ msgstr "" "Идентификатор версии, состоящий только из сегмента релиза и сегмента " "предрелиза, называется \"предрелизом\"." -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -25528,7 +25583,7 @@ msgstr "" "данного выпуска упорядочиваются сначала по фазе (альфа, бета, кандидат на " "выпуск), а затем по числовому компоненту в рамках этой фазы." -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." @@ -25537,7 +25592,7 @@ msgstr "" "выпуска, чтобы работать с некоторыми существующими устаревшими " "дистрибутивами." -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." @@ -25545,7 +25600,7 @@ msgstr "" "Утилиты установки ДОЛЖНЫ интерпретировать версии ``c`` как эквивалентные " "версиям ``rc`` (то есть, ``c1`` означает ту же версию, что и ``rc1``)." -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." @@ -25553,11 +25608,11 @@ msgstr "" "Средства сборки, средства публикации и индексные серверы ДОЛЖНЫ запрещать " "создание релизов ``rc`` и ``c`` для общего сегмента релиза." -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "Пост-релизы" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " @@ -25567,7 +25622,7 @@ msgstr "" "финальном релизе, которые не влияют на распространяемое ПО (например, " "исправление ошибки в примечаниях к релизу)." -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" @@ -25575,7 +25630,7 @@ msgstr "" "Если эти пост-релизы используются в рамках цикла разработки проекта, они " "обозначаются включением сегмента post-release в идентификатор версии::" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." @@ -25583,7 +25638,7 @@ msgstr "" "Идентификатор версии, включающий сегмент пост-релиза без сегмента релиза " "разработки, называется \"пост-релизом\"." -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -25595,7 +25650,7 @@ msgstr "" "составляющей, сразу после соответствующего релиза и перед любым последующим " "релизом." -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -25607,11 +25662,11 @@ msgstr "" "лучше использовать более длинный номер релиза и увеличивать последний " "компонент для каждого выпуска обслуживания." -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "Пост-релизы также разрешены для пре-релизов::" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -25622,11 +25677,11 @@ msgstr "" "это затрудняет разбор идентификатора версии для человека. В целом, гораздо " "понятнее просто создать новый пререлиз, увеличив числовой компонент." -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "Развивающие релизы" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -25638,7 +25693,7 @@ msgstr "" "релизы непосредственно из системы контроля исходных кодов, которые не будут " "конфликтовать с более поздними релизами проекта." -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " @@ -25648,7 +25703,7 @@ msgstr "" "указываются путем включения сегмента developmental release в идентификатор " "версии::" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." @@ -25656,7 +25711,7 @@ msgstr "" "Идентификатор версии, включающий сегмент выпуска разработки, называется " "\"выпуском разработки\"." -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -25670,14 +25725,14 @@ msgstr "" "перед любыми предшествующими релизами с тем же сегментом релиза) и после " "любого предыдущего релиза (включая любые пост-релизы)." -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" "Релизы разработки также разрешены для предварительных и последующих релизов::" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -25693,7 +25748,7 @@ msgstr "" "вместо этого создать новый предварительный релиз, увеличив числовой " "компонент." -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 msgid "" "Developmental releases of post-releases are also strongly discouraged, but " "they may be appropriate for projects which use the post-release notation for " @@ -25704,11 +25759,11 @@ msgstr "" "release для полных релизов сопровождения, которые могут включать изменения " "кода." -#: ../source/specifications/version-specifiers.rst:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "Эпохи версий" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 msgid "" "If included in a version identifier, the epoch appears before all other " "components, separated from the release segment by an exclamation mark::" @@ -25717,11 +25772,11 @@ msgstr "" "остальными компонентами и отделяется от сегмента релиза восклицательным " "знаком::" -#: ../source/specifications/version-specifiers.rst:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "Если явная эпоха не указана, то неявной эпохой будет ``0``." -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -25739,7 +25794,7 @@ msgstr "" "как ``1.0``, то новые релизы будут идентифицироваться как *более старые*, " "чем версии, основанные на дате, при использовании обычной схемы сортировки::" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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 " @@ -25749,11 +25804,11 @@ msgstr "" "сортировки: все версии, относящиеся к более поздней эпохе, будут " "отсортированы после версий, относящихся к более ранней эпохе::" -#: ../source/specifications/version-specifiers.rst:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "Нормализация" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -25765,11 +25820,11 @@ msgstr "" "версий. Эти синтаксисы ДОЛЖНЫ учитываться при разборе версии, однако они " "должны быть \"нормализованы\" к стандартному синтаксису, определенному выше." -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "Чувствительность случая" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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`` " @@ -25780,11 +25835,11 @@ msgstr "" "использовать такие версии, как ``1.1RC1``, которые будут нормализованы до " "``1.1rc1``." -#: ../source/specifications/version-specifiers.rst:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "Нормализация целого числа" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -25799,11 +25854,11 @@ msgstr "" "версии, например ``1.0+foo0100``, которая уже находится в нормализованной " "форме." -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "Сепараторы перед выпуском" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -25820,11 +25875,11 @@ msgstr "" "release и цифрой. Это позволяет использовать такие версии, как ``1.0a.1``, " "которые будут нормализованы до ``1.0a1``." -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "Предварительное написание" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -25840,11 +25895,11 @@ msgstr "" "``1.1a1``, ``1.1b2`` и ``1.1rc3``. В каждом случае дополнительные написания " "следует считать эквивалентными их нормальным формам." -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "Неявный номер предварительного выпуска" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -25856,11 +25911,11 @@ msgstr "" "``0``. Это позволяет использовать такие версии, как ``1.2a``, которые " "нормализуются до ``1.2a0``." -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "Сепараторы после выпуска" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -25878,11 +25933,11 @@ msgstr "" "обозначением пострелиза и цифрой. Это позволяет использовать версии типа " "``1.2.post-2``, которые нормализуются до ``1.2.post2``." -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "Написание после выпуска" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -25894,11 +25949,11 @@ msgstr "" "до ``1.0.post4``. Как и в предыдущих версиях, дополнительные написания " "следует считать эквивалентными их нормальным формам." -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "Неявный номер после выпуска" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -25910,11 +25965,11 @@ msgstr "" "позволяет использовать такие версии, как ``1.2.post``, которые нормализуются " "до ``1.2.post0``." -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "Неявные пост-релизы" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -25931,11 +25986,11 @@ msgstr "" "словами, ``1.0-`` - это *не* допустимая версия, и она *не* нормализуется до " "``1.0.post0``." -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "Сепараторы для выпуска продукции" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -25947,11 +26002,11 @@ msgstr "" "``.``. Это позволяет использовать такие версии, как ``1.2-dev2`` или " "``1.2dev2``, которые нормализуются до ``1.2.dev2``." -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "Номер выпуска неявной разработки" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -25963,11 +26018,11 @@ msgstr "" "``0``. Это позволяет использовать такие версии, как ``1.2.dev``, которые " "нормализуются до ``1.2.dev0``." -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "Сегменты локальной версии" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -25979,11 +26034,11 @@ msgstr "" "является использование символа ``.``. Это позволяет нормализовать такие " "версии, как ``1.0+ubuntu-1``, до ``1.0+ubuntu.1``." -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "Предшествующий символ v" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -25996,11 +26051,11 @@ msgstr "" "целей и должен быть опущен во всех нормализованных формах версии. Одна и та " "же версия с ``v`` и без него считается эквивалентной." -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "Ведущие и отслеживающие Белое пространство" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -26014,11 +26069,11 @@ msgstr "" "обрабатывать случайные пробелы, например, версия ``1.0\\n`` нормализуется до " "``1.0``." -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "Примеры совместимых схем версий" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -26034,7 +26089,7 @@ msgstr "" "относительный порядок версий, хотя приведенные выше правила гарантируют, что " "все совместимые инструменты будут упорядочивать их последовательно." -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -26046,22 +26101,22 @@ msgstr "" "гарантируя, что \"последний релиз\" и \"последний стабильный релиз\" могут " "быть легко определены как людьми, так и автоматизированными инструментами." -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "Простая версификация \"major.minor\" ::" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "Простая версия \"major.minor.micro\" ::" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" "Версии \"major.minor\" с предварительными выпусками альфа-версий, бета-" "версий и кандидатов::" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" @@ -26069,7 +26124,7 @@ msgstr "" "«major.minor»-версия с релизами, кандидатами на выпуск и пост-релизами для " "незначительных исправлений ::" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" @@ -26077,11 +26132,11 @@ msgstr "" "Релизы, основанные на дате, с использованием возрастающей серии в пределах " "каждого года, пропуская нулевой::" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "Краткое описание разрешенных суффиксов и относительного порядка" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 msgid "" "This section is intended primarily for authors of tools that automatically " "process distribution metadata, rather than developers of Python " @@ -26091,7 +26146,7 @@ msgstr "" "автоматически обрабатывающих метаданные дистрибутива, а не для разработчиков " "дистрибутивов Python, принимающих решение о выборе схемы версионирования." -#: ../source/specifications/version-specifiers.rst:617 +#: ../source/specifications/version-specifiers.rst:619 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 " @@ -26101,7 +26156,7 @@ msgstr "" "соответствии с числовым значением данной эпохи. Если сегмент эпохи " "отсутствует, неявное числовое значение равно ``0``." -#: ../source/specifications/version-specifiers.rst:621 +#: ../source/specifications/version-specifiers.rst:623 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 " @@ -26111,7 +26166,7 @@ msgstr "" "порядке, что и сортировка кортежей в Python, когда нормализованный сегмент " "выпуска разбирается следующим образом::" -#: ../source/specifications/version-specifiers.rst:627 +#: ../source/specifications/version-specifiers.rst:629 msgid "" "All release segments involved in the comparison MUST be converted to a " "consistent length by padding shorter segments with zeros as needed." @@ -26119,7 +26174,7 @@ msgstr "" "Все сегменты релиза, участвующие в сравнении, ДОЛЖНЫ быть приведены к единой " "длине путем заполнения более коротких сегментов нулями по мере необходимости." -#: ../source/specifications/version-specifiers.rst:630 +#: ../source/specifications/version-specifiers.rst:632 msgid "" "Within a numeric release (``1.0``, ``2.7.3``), the following suffixes are " "permitted and MUST be ordered as shown::" @@ -26127,7 +26182,7 @@ msgstr "" "В числовом выпуске (``1.0``, ``2.7.3``) разрешены следующие суффиксы, " "которые ДОЛЖНЫ быть упорядочены, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -26140,7 +26195,7 @@ msgstr "" "в одном сегменте выпуска как неоднозначный и остаться в соответствии со " "спецификацией." -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 msgid "" "Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate " "(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be " @@ -26150,7 +26205,7 @@ msgstr "" "(``1.0rc1``, ``1.0c1``) разрешены следующие суффиксы, которые ДОЛЖНЫ быть " "упорядочены, как показано::" -#: ../source/specifications/version-specifiers.rst:646 +#: ../source/specifications/version-specifiers.rst:648 msgid "" "Within a post-release (``1.0.post1``), the following suffixes are permitted " "and MUST be ordered as shown::" @@ -26158,7 +26213,7 @@ msgstr "" "Внутри пост-релиза (``1.0.post1``) разрешены следующие суффиксы, которые " "ДОЛЖНЫ быть упорядочены, как показано::" -#: ../source/specifications/version-specifiers.rst:651 +#: ../source/specifications/version-specifiers.rst:653 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." @@ -26168,7 +26223,7 @@ msgstr "" "точка, даже если они используются сразу после числовой версии (например, " "``1.0.dev456``, ``1.0.post1``)." -#: ../source/specifications/version-specifiers.rst:655 +#: ../source/specifications/version-specifiers.rst:657 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." @@ -26177,15 +26232,15 @@ msgstr "" "префиксом упорядочивание ДОЛЖНО осуществляться по значению числового " "компонента." -#: ../source/specifications/version-specifiers.rst:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "Следующий пример охватывает многие из возможных комбинаций::" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "Упорядочивание версий в различных версиях метаданных" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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 (:" @@ -26195,7 +26250,7 @@ msgstr "" "стандартную схему идентификации или упорядочивания версий. Однако в " "метаданных v1.2 (:pep:`345`) указана схема, которая определена в :pep:`386`." -#: ../source/specifications/version-specifiers.rst:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -26212,7 +26267,7 @@ msgstr "" "установить. Эти требования обуславливают необходимость стандартизации одного " "механизма разбора, который будет использоваться для всех версий проекта." -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -26228,7 +26283,7 @@ msgstr "" "и упорядочивания версий, определенным реализацией, если версии, " "соответствующие этой спецификации, недоступны." -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." @@ -26236,11 +26291,11 @@ msgstr "" "Пользователи дистрибутива могут захотеть явно удалить несоответствующие " "версии из всех частных индексов пакетов, которые они контролируют." -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "Совместимость с другими схемами версий" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -26253,7 +26308,7 @@ msgstr "" "спецификации. В таких случаях версия для конкретного проекта может храниться " "в метаданных, а переведенная публичная версия публикуется в поле версии." -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 msgid "" "This allows automated distribution tools to provide consistently correct " "ordering of published releases, while still allowing developers to use the " @@ -26264,7 +26319,7 @@ msgstr "" "позволяя разработчикам использовать внутреннюю схему версионирования, " "которую они предпочитают для своих проектов." -#: ../source/specifications/version-specifiers.rst:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -26282,7 +26337,7 @@ msgstr "" "дистрибутивов, а также при публикации дистрибутива, на который полагаются " "другие." -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -26294,7 +26349,7 @@ msgstr "" "полностью совместимы со схемой версий, определенной в данной спецификации, и " "соблюдение этих аспектов приветствуется." -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 msgid "" "Semantic versions containing a hyphen (pre-releases - clause 10) or a plus " "sign (builds - clause 11) are *not* compatible with this specification and " @@ -26304,7 +26359,7 @@ msgstr "" "(бабочки - пункт 11), не совместимы с этой спецификацией и не разрешены в " "поле публичной версии." -#: ../source/specifications/version-specifiers.rst:739 +#: ../source/specifications/version-specifiers.rst:741 msgid "" "One possible mechanism to translate such semantic versioning based source " "labels to compatible public versions is to use the ``.devN`` suffix to " @@ -26315,18 +26370,18 @@ msgstr "" "использование суффикса ``.devN`` для указания соответствующего порядка " "версий." -#: ../source/specifications/version-specifiers.rst:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" "Информация о конкретной сборке также может быть включена в локальные метки " "версий." -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "Метки версий на базе DVCS" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -26338,7 +26393,7 @@ msgstr "" "идентификатору версии. Поскольку хэши не могут быть надежно упорядочены, " "такие версии не допускаются в поле публичной версии." -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 msgid "" "As with semantic versioning, the public ``.devN`` suffix may be used to " "uniquely identify such releases for publication, while the original DVCS " @@ -26349,18 +26404,18 @@ msgstr "" "публикации, а оригинальная метка, основанная на DVCS, может храниться в " "метаданных проекта." -#: ../source/specifications/version-specifiers.rst:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" "Идентифицирующая хэш-информация также может быть включена в метки локальных " "версий." -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "Версия базы данных Олсона" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 msgid "" "The ``pytz`` project inherits its versioning scheme from the corresponding " "Olson timezone database versioning scheme: the year followed by a lowercase " @@ -26370,7 +26425,7 @@ msgstr "" "базы данных часового пояса Olson: год, за которым следует строчный символ, " "указывающий на версию базы данных в пределах этого года." -#: ../source/specifications/version-specifiers.rst:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -26382,7 +26437,7 @@ msgstr "" "'<год>a') и увеличивается с каждым последующим обновлением базы данных в " "течение года." -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 msgid "" "As with other translated version identifiers, the corresponding Olson " "database version could be recorded in the project metadata." @@ -26391,7 +26446,7 @@ msgstr "" "соответствующая версия базы данных Olson может быть записана в метаданных " "проекта." -#: ../source/specifications/version-specifiers.rst:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" @@ -26399,35 +26454,35 @@ msgstr "" "Спецификатор версии состоит из ряда пунктов версии, разделенных запятыми. " "Например::" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "Оператор сравнения определяет тип положения версии:" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "``~=``: `Совместимый релиз`_ пункт" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "``==``: `Версия соответствует`_ пункту" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "``!=``: `исключение версии`_ пункт" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "``<=``, ``>=``: предложение ``включенного упорядоченного сравнения`_" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "``<``, ``>``: предложение ``исключительного упорядоченного сравнения``" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "``===``: предложение `произвольного равенства`." -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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 " @@ -26437,7 +26492,7 @@ msgstr "" "должна соответствовать всем заданным пунктам версии, чтобы соответствовать " "спецификатору в целом." -#: ../source/specifications/version-specifiers.rst:800 +#: ../source/specifications/version-specifiers.rst:802 msgid "" "Whitespace between a conditional operator and the following version " "identifier is optional, as is the whitespace around the commas." @@ -26445,7 +26500,7 @@ msgstr "" "Пробелы между условным оператором и следующим идентификатором версии " "необязательны, как и пробелы вокруг запятых." -#: ../source/specifications/version-specifiers.rst:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -26460,7 +26515,7 @@ msgstr "" "кандидатов, ДОЛЖЕН решаться в соответствии с описанием в `Обработке " "предварительных выпусков`_." -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 msgid "" "Except where specifically noted below, local version identifiers MUST NOT be " "permitted in version specifiers, and local version labels MUST be ignored " @@ -26471,11 +26526,11 @@ msgstr "" "ДОЛЖНЫ полностью игнорироваться при проверке соответствия версий-кандидатов " "заданному спецификатору версий." -#: ../source/specifications/version-specifiers.rst:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "Совместимый выпуск" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 msgid "" "A compatible release clause consists of the compatible release operator " "``~=`` and a version identifier. It matches any candidate version that is " @@ -26485,7 +26540,7 @@ msgstr "" "``~=`` и идентификатора версии. Он соответствует любой версии-кандидату, " "которая, как ожидается, будет совместима с указанной версией." -#: ../source/specifications/version-specifiers.rst:824 +#: ../source/specifications/version-specifiers.rst:826 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_. Local version identifiers are NOT permitted in this " @@ -26495,7 +26550,7 @@ msgstr "" "в `Схема версии`_. Локальные идентификаторы версий в этом спецификаторе " "версий НЕ допускаются." -#: ../source/specifications/version-specifiers.rst:828 +#: ../source/specifications/version-specifiers.rst:830 msgid "" "For a given release identifier ``V.N``, the compatible release clause is " "approximately equivalent to the pair of comparison clauses::" @@ -26503,7 +26558,7 @@ msgstr "" "Для данного идентификатора выпуска ``V.N`` совместимое положение о выпуске " "приблизительно эквивалентно паре положений сравнения::" -#: ../source/specifications/version-specifiers.rst:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." @@ -26511,11 +26566,11 @@ msgstr "" "Этот оператор НЕ ДОЛЖЕН использоваться с номером версии одного сегмента, " "таким как ``~=1``." -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "Например, следующие группы положений о версии эквивалентны::" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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 " @@ -26525,7 +26580,7 @@ msgstr "" "совместимом релизе как ``V.N.suffix``, то суффикс игнорируется при " "определении требуемого соответствия префикса::" -#: ../source/specifications/version-specifiers.rst:854 +#: ../source/specifications/version-specifiers.rst:856 msgid "" "The padding rules for release segment comparisons means that the assumed " "degree of forward compatibility in a compatible release clause can be " @@ -26536,11 +26591,11 @@ msgstr "" "контролироваться путем добавления дополнительных нулей к спецификатору " "версии::" -#: ../source/specifications/version-specifiers.rst:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "Соответствие версий" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." @@ -26548,7 +26603,7 @@ msgstr "" "Условие сопоставления версий включает оператор сопоставления версий ``==`` и " "идентификатор версии." -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 msgid "" "The specified version identifier must be in the standard format described in " "`Version scheme`_, but a trailing ``.*`` is permitted on public version " @@ -26558,7 +26613,7 @@ msgstr "" "в `Version scheme`_, но в идентификаторах публичных версий допускается " "наличие конца ``.*``, как описано ниже." -#: ../source/specifications/version-specifiers.rst:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -26571,7 +26626,7 @@ msgstr "" "Единственная выполняемая замена - это нулевое заполнение сегмента выпуска, " "чтобы гарантировать, что сегменты выпуска сравниваются с одинаковой длиной." -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -26583,7 +26638,7 @@ msgstr "" "ДОЛЖНЫ как минимум выдавать предупреждения, а могут и полностью отклонять " "их, если строгое соответствие версий используется неуместно." -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -26600,8 +26655,8 @@ msgstr "" "то сдерживающие компоненты (или их отсутствие) в сегменте релиза также " "игнорируются." -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" @@ -26609,7 +26664,7 @@ msgstr "" "Например, для версии ``1.1.post1`` следующие пункты будут совпадать или не " "совпадать, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 msgid "" "For purposes of prefix matching, the pre-release segment is considered to " "have an implied preceding ``.``, so given the version ``1.1a1``, the " @@ -26619,7 +26674,7 @@ msgstr "" "подразумеваемый предшествующий ``.``, поэтому, учитывая версию ``1.1a1``, " "следующие фразы будут соответствовать или не соответствовать, как показано::" -#: ../source/specifications/version-specifiers.rst:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -26631,7 +26686,7 @@ msgstr "" "сегмента release в идентификаторах версий). Для версии ``1.1`` следующие " "пункты будут совпадать или не совпадать, как показано на рисунке::" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -26646,7 +26701,7 @@ msgstr "" "сравнения, поэтому использование любого из них в префиксном совпадении не " "имеет смысла." -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -26662,7 +26717,7 @@ msgstr "" "при определении зависимостей для повторяющихся *развертываний приложений* " "при использовании общего индекса дистрибутива." -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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 " @@ -26672,7 +26727,7 @@ msgstr "" "версии (без метки локальной версии), то метка локальной версии любых версий-" "кандидатов ДОЛЖНА игнорироваться при сопоставлении версий." -#: ../source/specifications/version-specifiers.rst:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -26686,11 +26741,11 @@ msgstr "" "сопоставляется, как описано выше, а метка локальной версии проверяется на " "эквивалентность с помощью строгого сравнения равенства строк." -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "Исключение версии" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." @@ -26698,7 +26753,7 @@ msgstr "" "Предложение об исключении версии включает оператор исключения версии ``!=`` " "и идентификатор версии." -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 msgid "" "The allowed version identifiers and comparison semantics are the same as " "those of the `Version matching`_ operator, except that the sense of any " @@ -26708,11 +26763,11 @@ msgstr "" "оператора `Version matching`_, за исключением того, что смысл любого " "совпадения инвертируется." -#: ../source/specifications/version-specifiers.rst:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "Всеобъемлющее упорядоченное сравнение" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -26726,12 +26781,12 @@ msgstr "" "указанной версии с учетом последовательного упорядочивания, определенного " "стандартной `Version scheme`_." -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "Инклюзивные операторы упорядоченного сравнения - ``<=`` и ``>=``." -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 msgid "" "As with version matching, the release segment is zero padded as necessary to " "ensure the release segments are compared with the same length." @@ -26739,17 +26794,17 @@ msgstr "" "Как и при сопоставлении версий, сегмент выпуска обнуляется по мере " "необходимости, чтобы сегменты выпуска сравнивались с одинаковой длиной." -#: ../source/specifications/version-specifiers.rst:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" "Локальные идентификаторы версий в этом спецификаторе версий НЕ допускаются." -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "Исключительное упорядоченное сравнение" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -26765,7 +26820,7 @@ msgstr "" "специально исключают пре-релизы, пост-релизы и локальные версии указанной " "версии." -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -26781,7 +26836,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:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." @@ -26789,7 +26844,7 @@ msgstr "" "Исключительное упорядоченное сравнение ``>V`` **НЕ ДОЛЖНО** соответствовать " "локальной версии указанной версии." -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " @@ -27085,7 +27140,7 @@ msgstr "" "указано путем включения записи ``=`` в " "качестве части фрагмента URL." -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -27100,7 +27155,7 @@ msgstr "" "МОГУТ не выдавать предупреждения об отсутствии хэшей для систем контроля " "версий, которые не предоставляют идентификаторы фиксации на основе хэшей." -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -27112,7 +27167,7 @@ msgstr "" "добавлена в конец URL с помощью нотации ``@`` или " "``@#``." -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -27129,15 +27184,15 @@ msgstr "" "хэш, чтобы затруднить подделку (создать вредоносное репо с определённым " "тегом легко, а создать репо с определённым *хэшем* - менее)." -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "Примеры удаленных URL::" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "URL-адреса файлов" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -27150,7 +27205,7 @@ msgstr "" "определяет путь к файлу в файловой системе, к которому необходимо получить " "доступ." -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -27163,7 +27218,7 @@ msgstr "" "в \\*nix схема ``file://`` может использоваться только для доступа к путям " "на локальной машине." -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -27183,11 +27238,11 @@ msgstr "" "в Windows можно найти в `MSDN `_." -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "Краткое описание отличий от pkg_resources.parse_version" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 #, fuzzy #| msgid "" #| "Note: this comparison is to ``pkg_resourses.parse_version`` as it existed " @@ -27203,7 +27258,7 @@ msgstr "" "был принят, setuptools 6.0 и более поздние версии приняли описанное здесь " "поведение." -#: ../source/specifications/version-specifiers.rst:1185 +#: ../source/specifications/version-specifiers.rst:1187 msgid "" "Local versions sort differently, this specification requires that they sort " "as greater than the same version without a local version, whereas " @@ -27213,7 +27268,7 @@ msgstr "" "сортировались как большие, чем та же версия без локальной версии, в то время " "как ``pkg_resources.parse_version`` считает это маркером предрелизности." -#: ../source/specifications/version-specifiers.rst:1189 +#: ../source/specifications/version-specifiers.rst:1191 msgid "" "This specification purposely restricts the syntax which constitutes a valid " "version while ``pkg_resources.parse_version`` attempts to provide some " @@ -27223,7 +27278,7 @@ msgstr "" "собой правильную версию, в то время как ``pkg_resources.parse_version`` " "пытается получить некоторое значение из *любой* произвольной строки." -#: ../source/specifications/version-specifiers.rst:1193 +#: ../source/specifications/version-specifiers.rst:1195 msgid "" "``pkg_resources.parse_version`` allows arbitrarily deeply nested version " "signifiers like ``1.0.dev1.post1.dev5``. This specification however allows " @@ -27234,11 +27289,11 @@ msgstr "" "допускает только одно использование каждого типа, и они должны существовать " "в определенном порядке." -#: ../source/specifications/version-specifiers.rst:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "Приложение: Разбор строк версий с помощью регулярных выражений" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -27252,7 +27307,7 @@ msgstr "" "использовать для проверки того, имеет ли версия уже такую форму, и, если " "нет, извлечь различные компоненты для последующей нормализации." -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" @@ -27260,7 +27315,7 @@ msgstr "" "Чтобы проверить, соответствует ли идентификатор версии каноническому " "формату, можно воспользоваться следующей функцией:" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 msgid "" "To extract the components of a version identifier, use the following regular " "expression (as defined by the `packaging `_):" -#: ../source/specifications/version-specifiers.rst:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "Август 2014 г: Эта спецификация была одобрена через :pep:`440`." @@ -27382,6 +27437,336 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "Май 2012 г: Эта спецификация была одобрена через :pep:`405`." +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Pyproject Metadata" +msgid "Well-known Project URLs in Metadata" +msgstr "Метаданные Pyproject" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +#, fuzzy +#| msgid "" +#| "This specification was originally defined in :pep:`518` and :pep:`621`." +msgid "This specification was originally defined in :pep:`753`." +msgstr "" +"Эта спецификация была первоначально определена в :pep:`518` и :pep:`621`." + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +#| msgid "Name normalization" +msgid "Label normalization" +msgstr "Нормализация имен" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +#| msgid "Normalized Names" +msgid "Normalized" +msgstr "Нормализованные названия" + +#: ../source/specifications/well-known-project-urls.rst:76 +#, fuzzy +#| msgid "Home-page" +msgid "``Homepage``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +#, fuzzy +#| msgid "Home-page" +msgid "``homepage``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:78 +#, fuzzy +#| msgid "Home-page" +msgid "``Home-page``" +msgstr "Home-page" + +#: ../source/specifications/well-known-project-urls.rst:80 +#, fuzzy +#| msgid "Home page" +msgid "``Home page``" +msgstr "Домашняя страница" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +#, fuzzy +#| msgid "Creating documentation" +msgid "``documentation`` (Documentation)" +msgstr "Создание документации" + +#: ../source/specifications/well-known-project-urls.rst:124 +#, fuzzy +#| msgid "Creating documentation" +msgid "The project's online documentation" +msgstr "Создание документации" + +#: ../source/specifications/well-known-project-urls.rst:125 +#, fuzzy +#| msgid "``upload_docs``" +msgid "``docs``" +msgstr "``upload_docs``" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +#| msgid "Basic information" +msgid "Funding Information" +msgstr "Базовая информация" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +#| msgid "Example" +msgid "Example behavior" +msgstr "Пример" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +#, fuzzy +#| msgid "Core metadata specifications" +msgid "Core metadata representation" +msgstr "Спецификации основных метаданных" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "Как получить поддержку" @@ -29149,6 +29534,12 @@ msgstr "" "Если вы только начинаете с Python упаковки, рекомендуется придерживаться " "*регулярных пакетов* и ``__init__.py`` (даже если файл пуст)." +#~ msgid "" +#~ "A table of URLs where the key is the URL label and the value is the URL " +#~ "itself." +#~ msgstr "" +#~ "Таблица URL-адресов, где ключом является метка URL, а значением - сам URL." + #~ msgid "Update this page for build backends other than setuptools." #~ msgstr "Обновите эту страницу для бэкендов сборки, отличных от setuptools." diff --git a/locales/sai/LC_MESSAGES/messages.po b/locales/sai/LC_MESSAGES/messages.po index f7e3dce53..625ee245f 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/si/LC_MESSAGES/messages.po b/locales/si/LC_MESSAGES/messages.po index 25a24b84d..ea7110b76 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2022-06-11 08:19+0000\n" "Last-Translator: Kushan Gunasekera \n" "Language-Team: Sinhala `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3175,13 +3174,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8653,7 +8653,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8853,45 +8853,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12169,7 +12199,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12178,11 +12208,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12304,15 +12334,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12411,16 +12441,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12611,94 +12641,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12706,7 +12717,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12716,33 +12727,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12750,50 +12761,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12801,64 +12812,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12866,13 +12877,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12880,36 +12891,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12918,13 +12937,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12932,20 +12951,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12953,7 +12972,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12963,11 +12982,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12975,7 +12994,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12985,18 +13004,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13005,7 +13024,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13016,63 +13035,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13083,33 +13127,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13118,89 +13162,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16110,7 +16154,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16362,24 +16406,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16387,14 +16432,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16402,7 +16447,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16410,24 +16455,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16435,7 +16480,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16446,17 +16491,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16464,19 +16509,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16485,20 +16530,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16506,18 +16551,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16525,7 +16570,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16533,14 +16578,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18576,7 +18621,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18909,29 +18954,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18939,48 +18984,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18988,7 +19033,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18996,11 +19041,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19008,11 +19053,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19020,20 +19065,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19042,13 +19087,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19058,28 +19103,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19090,18 +19135,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19109,22 +19154,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19133,11 +19178,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19147,11 +19192,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19161,11 +19206,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19173,11 +19218,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19188,11 +19233,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19200,11 +19245,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19212,11 +19257,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19226,11 +19271,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19238,11 +19283,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19250,11 +19295,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19262,11 +19307,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19275,11 +19320,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19288,11 +19333,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19302,7 +19347,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19310,69 +19355,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19380,48 +19425,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19432,7 +19477,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19442,17 +19487,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19461,14 +19506,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19479,7 +19524,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19487,30 +19532,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19518,30 +19563,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19549,60 +19594,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19611,79 +19656,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19692,7 +19737,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19700,7 +19745,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19710,21 +19755,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19732,7 +19777,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19741,7 +19786,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19751,14 +19796,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19767,28 +19812,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19797,27 +19842,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19827,7 +19872,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19837,13 +19882,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20063,7 +20108,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20071,7 +20116,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20082,15 +20127,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20098,7 +20143,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20106,7 +20151,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20118,43 +20163,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20163,20 +20208,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20254,6 +20299,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index 923fcfb50..2f65c6044 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-04-25 06:07+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Slovak `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3295,13 +3294,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8809,7 +8809,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -9009,45 +9009,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12325,7 +12355,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12334,11 +12364,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12460,15 +12490,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12567,16 +12597,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12767,94 +12797,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Udržiavač" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12862,7 +12873,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12872,33 +12883,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12906,50 +12917,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12957,64 +12968,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13022,13 +13033,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13036,36 +13047,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13074,13 +13093,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13088,20 +13107,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13109,7 +13128,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13119,11 +13138,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13131,7 +13150,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13141,18 +13160,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13161,7 +13180,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13172,63 +13191,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13239,33 +13283,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13274,89 +13318,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16272,7 +16316,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16524,24 +16568,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16549,14 +16594,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16564,7 +16609,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16572,24 +16617,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16597,7 +16642,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16608,17 +16653,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16626,19 +16671,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16647,20 +16692,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16668,18 +16713,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16687,7 +16732,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16695,14 +16740,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18744,7 +18789,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19079,29 +19124,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19109,48 +19154,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19158,7 +19203,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19166,11 +19211,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19178,11 +19223,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19190,20 +19235,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19212,13 +19257,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19228,28 +19273,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19260,18 +19305,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19279,22 +19324,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19303,11 +19348,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19317,11 +19362,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19331,11 +19376,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19343,11 +19388,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19358,11 +19403,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19370,11 +19415,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19382,11 +19427,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19396,11 +19441,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19408,11 +19453,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19420,11 +19465,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19432,11 +19477,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19445,11 +19490,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19458,11 +19503,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19472,7 +19517,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19480,69 +19525,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19550,48 +19595,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19602,7 +19647,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19612,17 +19657,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19631,14 +19676,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19649,7 +19694,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19657,30 +19702,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19688,30 +19733,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19719,60 +19764,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19781,79 +19826,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19862,7 +19907,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19870,7 +19915,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19880,21 +19925,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19902,7 +19947,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19911,7 +19956,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19921,14 +19966,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19937,28 +19982,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19967,27 +20012,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19997,7 +20042,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20007,13 +20052,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20233,7 +20278,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20241,7 +20286,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20252,15 +20297,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20268,7 +20313,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20276,7 +20321,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20288,43 +20333,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20333,20 +20378,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20424,6 +20469,308 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "Meno projektu" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/ta/LC_MESSAGES/messages.po b/locales/ta/LC_MESSAGES/messages.po index 1607d1e36..78b363574 100644 --- a/locales/ta/LC_MESSAGES/messages.po +++ b/locales/ta/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -2013,7 +2013,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2190,31 +2190,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3171,13 +3170,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8649,7 +8649,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8849,45 +8849,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12165,7 +12195,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12174,11 +12204,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12300,15 +12330,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12407,16 +12437,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12607,94 +12637,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12702,7 +12713,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12712,33 +12723,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12746,50 +12757,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12797,64 +12808,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12862,13 +12873,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12876,36 +12887,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12914,13 +12933,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12928,20 +12947,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12949,7 +12968,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12959,11 +12978,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12971,7 +12990,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12981,18 +13000,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13001,7 +13020,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13012,63 +13031,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13079,33 +13123,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13114,89 +13158,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16106,7 +16150,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16358,24 +16402,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16383,14 +16428,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16398,7 +16443,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16406,24 +16451,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16431,7 +16476,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16442,17 +16487,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16460,19 +16505,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16481,20 +16526,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16502,18 +16547,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16521,7 +16566,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16529,14 +16574,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18572,7 +18617,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18905,29 +18950,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18935,48 +18980,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18984,7 +19029,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18992,11 +19037,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19004,11 +19049,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19016,20 +19061,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19038,13 +19083,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19054,28 +19099,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19086,18 +19131,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19105,22 +19150,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19129,11 +19174,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19143,11 +19188,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19157,11 +19202,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19169,11 +19214,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19184,11 +19229,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19196,11 +19241,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19208,11 +19253,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19222,11 +19267,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19234,11 +19279,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19246,11 +19291,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19258,11 +19303,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19271,11 +19316,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19284,11 +19329,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19298,7 +19343,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19306,69 +19351,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19376,48 +19421,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19428,7 +19473,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19438,17 +19483,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19457,14 +19502,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19475,7 +19520,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19483,30 +19528,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19514,30 +19559,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19545,60 +19590,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19607,79 +19652,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19688,7 +19733,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19696,7 +19741,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19706,21 +19751,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19728,7 +19773,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19737,7 +19782,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19747,14 +19792,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19763,28 +19808,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19793,27 +19838,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19823,7 +19868,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19833,13 +19878,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20059,7 +20104,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20067,7 +20112,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20078,15 +20123,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20094,7 +20139,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20102,7 +20147,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20114,43 +20159,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20159,20 +20204,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20250,6 +20295,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/tr/LC_MESSAGES/messages.po b/locales/tr/LC_MESSAGES/messages.po index 0884705f3..e02eb842e 100644 --- a/locales/tr/LC_MESSAGES/messages.po +++ b/locales/tr/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-10-16 20:19+0000\n" "Last-Translator: Emr \n" "Language-Team: Turkish `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3174,13 +3173,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8652,7 +8652,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8852,45 +8852,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12168,7 +12198,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12177,11 +12207,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12303,15 +12333,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12410,16 +12440,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12610,94 +12640,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12705,7 +12716,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12715,33 +12726,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12749,50 +12760,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12800,64 +12811,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12865,13 +12876,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12879,36 +12890,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12917,13 +12936,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12931,20 +12950,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12952,7 +12971,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12962,11 +12981,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12974,7 +12993,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -12984,18 +13003,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13004,7 +13023,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13015,63 +13034,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13082,33 +13126,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13117,89 +13161,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16109,7 +16153,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16361,24 +16405,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16386,14 +16431,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16401,7 +16446,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16409,24 +16454,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16434,7 +16479,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16445,17 +16490,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16463,19 +16508,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16484,20 +16529,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16505,18 +16550,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16524,7 +16569,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16532,14 +16577,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18575,7 +18620,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18908,29 +18953,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18938,48 +18983,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -18987,7 +19032,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -18995,11 +19040,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19007,11 +19052,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19019,20 +19064,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19041,13 +19086,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19057,28 +19102,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19089,18 +19134,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19108,22 +19153,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19132,11 +19177,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19146,11 +19191,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19160,11 +19205,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19172,11 +19217,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19187,11 +19232,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19199,11 +19244,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19211,11 +19256,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19225,11 +19270,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19237,11 +19282,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19249,11 +19294,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19261,11 +19306,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19274,11 +19319,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19287,11 +19332,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19301,7 +19346,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19309,69 +19354,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19379,48 +19424,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19431,7 +19476,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19441,17 +19486,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19460,14 +19505,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19478,7 +19523,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19486,30 +19531,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19517,30 +19562,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19548,60 +19593,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19610,79 +19655,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19691,7 +19736,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19699,7 +19744,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19709,21 +19754,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19731,7 +19776,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19740,7 +19785,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19750,14 +19795,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19766,28 +19811,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19796,27 +19841,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19826,7 +19871,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19836,13 +19881,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20062,7 +20107,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20070,7 +20115,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20081,15 +20126,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20097,7 +20142,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20105,7 +20150,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20117,43 +20162,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20162,20 +20207,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20253,6 +20298,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/uk/LC_MESSAGES/messages.po b/locales/uk/LC_MESSAGES/messages.po index 13060e44f..ea49c71fd 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-03-01 20:00+0000\n" "Last-Translator: Sviatoslav Sydorenko \n" "Language-Team: Ukrainian `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3554,13 +3553,14 @@ msgstr "Стовпець" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "Опис" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "Приклади" @@ -9148,7 +9148,7 @@ msgid "Dependencies and requirements" msgstr "install_requires проти файлів requirements" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "``dependencies``/``optional-dependencies``" @@ -9348,47 +9348,77 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "``urls``" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 #, fuzzy #| msgid "For example:" msgid "A full example" msgstr "Наприклад:" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12686,7 +12716,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12695,11 +12725,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12821,15 +12851,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "Приклад::" @@ -12928,16 +12958,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "Приклади::" @@ -13128,94 +13158,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "Author" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "Author-email" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "Доглядач" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "Maintainer-email" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "License" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -13223,7 +13234,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -13233,33 +13244,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -13267,50 +13278,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -13318,64 +13329,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13383,13 +13394,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13397,36 +13408,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13435,13 +13454,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13449,20 +13468,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13470,7 +13489,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13480,11 +13499,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13492,7 +13511,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13502,18 +13521,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13522,7 +13541,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13533,65 +13552,90 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 #, fuzzy #| msgid "Requirements files" msgid "Requires" msgstr "Файли requirements" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13602,33 +13646,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13637,89 +13681,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16681,7 +16725,7 @@ msgid "``dependencies``" msgstr "Перевизначення залежностей" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "``dynamic``" @@ -16936,24 +16980,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16961,14 +17006,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16976,7 +17021,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16984,24 +17029,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -17009,7 +17054,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -17020,17 +17065,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -17038,19 +17083,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -17059,20 +17104,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -17080,18 +17125,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -17099,7 +17144,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -17107,14 +17152,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -19170,7 +19215,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19508,31 +19553,31 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 #, fuzzy #| msgid "Pre-release versioning" msgid "Pre-releases" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19540,50 +19585,50 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 #, fuzzy #| msgid "zest.releaser" msgid "Post-releases" msgstr "zest.releaser" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19591,7 +19636,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19599,11 +19644,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19611,11 +19656,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19623,20 +19668,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19645,13 +19690,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19661,29 +19706,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19694,19 +19739,19 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 #, fuzzy msgid "Normalization" msgstr "Переклади" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19714,23 +19759,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "Переклади" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19739,13 +19784,13 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 #, fuzzy #| msgid "Pre-release versioning" msgid "Pre-release separators" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19755,13 +19800,13 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 #, fuzzy #| msgid "Pre-release versioning" msgid "Pre-release spelling" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19771,11 +19816,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19783,11 +19828,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19798,13 +19843,13 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 #, fuzzy #| msgid "Pre-release versioning" msgid "Post release spelling" msgstr "Версіонування попередніх випусків" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19812,11 +19857,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19824,11 +19869,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19838,11 +19883,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19850,11 +19895,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19862,13 +19907,13 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 #, fuzzy #| msgid "Local version identifiers" msgid "Local version segments" msgstr "Ідентифікатори місцевих версій" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19876,11 +19921,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19889,11 +19934,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19902,13 +19947,13 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 #, fuzzy #| msgid "Here are some examples of compliant version numbers::" msgid "Examples of compliant version schemes" msgstr "Ось кілька прикладів сумісних номерів версій::" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19918,7 +19963,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19926,71 +19971,71 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 #, fuzzy #| msgid "Serial versioning" msgid "Simple \"major.minor\" versioning::" msgstr "Порядкове версіонування" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19998,48 +20043,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -20050,7 +20095,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -20060,17 +20105,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -20079,14 +20124,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -20097,7 +20142,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -20105,32 +20150,32 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 #, fuzzy #| msgid "Date based versioning" msgid "DVCS based version labels" msgstr "Версіонування базоване на датах" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -20138,32 +20183,32 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 #, fuzzy #| msgid "Date based versioning" msgid "Olson database versioning" msgstr "Версіонування базоване на датах" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -20171,60 +20216,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -20233,81 +20278,81 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 #, fuzzy #| msgid "Version" msgid "Version matching" msgstr "Version" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -20316,7 +20361,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -20324,7 +20369,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -20334,21 +20379,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -20356,7 +20401,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -20365,7 +20410,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -20375,14 +20420,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -20391,30 +20436,30 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy #| msgid "Version Specifier" msgid "Version exclusion" msgstr "Специфікатор версії" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -20423,27 +20468,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -20453,7 +20498,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20463,13 +20508,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20689,7 +20734,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20697,7 +20742,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20708,17 +20753,17 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 #, fuzzy #| msgid "For example::" msgid "Remote URL examples::" msgstr "Наприклад::" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20726,7 +20771,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20734,7 +20779,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20746,43 +20791,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20791,20 +20836,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20882,6 +20927,321 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "Назва проєкту" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "Переклади" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "Переклади" + +#: ../source/specifications/well-known-project-urls.rst:76 +#, fuzzy +#| msgid "Home page" +msgid "``Homepage``" +msgstr "Домашня сторінка" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +#, fuzzy +#| msgid "Home page" +msgid "``homepage``" +msgstr "Домашня сторінка" + +#: ../source/specifications/well-known-project-urls.rst:78 +#, fuzzy +#| msgid "Home page" +msgid "``Home-page``" +msgstr "Домашня сторінка" + +#: ../source/specifications/well-known-project-urls.rst:80 +#, fuzzy +#| msgid "Home page" +msgid "``Home page``" +msgstr "Домашня сторінка" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +#| msgid "Additional tools" +msgid "Funding Information" +msgstr "Додаткові інструменти" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +msgid "Example behavior" +msgstr "Приклади" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/vi/LC_MESSAGES/messages.po b/locales/vi/LC_MESSAGES/messages.po index 73ba0e651..e5962e8d4 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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-07-25 13:10+0000\n" "Last-Translator: Lenny Tran \n" "Language-Team: Vietnamese `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3199,13 +3198,14 @@ msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "" @@ -8677,7 +8677,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8877,45 +8877,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:444 +msgid "" +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12193,7 +12223,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12202,11 +12232,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12328,15 +12358,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -12435,16 +12465,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "" @@ -12635,94 +12665,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12730,7 +12741,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12740,33 +12751,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12774,50 +12785,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12825,64 +12836,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12890,13 +12901,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12904,36 +12915,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -12942,13 +12961,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -12956,20 +12975,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -12977,7 +12996,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -12987,11 +13006,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -12999,7 +13018,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13009,18 +13028,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13029,7 +13048,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13040,63 +13059,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13107,33 +13151,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13142,89 +13186,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16134,7 +16178,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16386,24 +16430,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16411,14 +16456,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16426,7 +16471,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16434,24 +16479,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16459,7 +16504,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16470,17 +16515,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16488,19 +16533,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16509,20 +16554,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16530,18 +16575,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16549,7 +16594,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16557,14 +16602,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18600,7 +18645,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -18933,29 +18978,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -18963,48 +19008,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19012,7 +19057,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19020,11 +19065,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19032,11 +19077,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19044,20 +19089,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19066,13 +19111,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19082,28 +19127,28 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 msgid "Version epochs" msgstr "" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19114,18 +19159,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19133,22 +19178,22 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 msgid "Integer Normalization" msgstr "" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19157,11 +19202,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19171,11 +19216,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19185,11 +19230,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19197,11 +19242,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19212,11 +19257,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19224,11 +19269,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19236,11 +19281,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19250,11 +19295,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19262,11 +19307,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19274,11 +19319,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19286,11 +19331,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19299,11 +19344,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19312,11 +19357,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19326,7 +19371,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19334,69 +19379,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19404,48 +19449,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19456,7 +19501,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19466,17 +19511,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19485,14 +19530,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19503,7 +19548,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19511,30 +19556,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19542,30 +19587,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19573,60 +19618,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19635,79 +19680,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19716,7 +19761,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19724,7 +19769,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19734,21 +19779,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19756,7 +19801,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19765,7 +19810,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19775,14 +19820,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19791,28 +19836,28 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 msgid "Version exclusion" msgstr "" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19821,27 +19866,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19851,7 +19896,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19861,13 +19906,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20087,7 +20132,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20095,7 +20140,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20106,15 +20151,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20122,7 +20167,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20130,7 +20175,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20142,43 +20187,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20187,20 +20232,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20278,6 +20323,306 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +msgid "Well-known Project URLs in Metadata" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +msgid "Label normalization" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +msgid "Normalized" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" diff --git a/locales/zh_Hans/LC_MESSAGES/messages.po b/locales/zh_Hans/LC_MESSAGES/messages.po index c2cd2e2f5..fe5e8bd9e 100644 --- a/locales/zh_Hans/LC_MESSAGES/messages.po +++ b/locales/zh_Hans/LC_MESSAGES/messages.po @@ -30,7 +30,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-09-21 00:40+0000\n" "Last-Translator: 大王叫我来巡山 \n" @@ -2234,7 +2234,7 @@ msgid "" msgstr "" #: ../source/discussions/versioning.rst:84 -#: ../source/specifications/version-specifiers.rst:721 +#: ../source/specifications/version-specifiers.rst:723 msgid "Semantic versioning" msgstr "" @@ -2412,31 +2412,30 @@ msgstr "" #: ../source/discussions/versioning.rst:202 msgid "" "As import packages and modules are not *required* to publish runtime version " -"information in this way (see the rejected proposal in :pep:`PEP 396 <396>`), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3492,13 +3491,14 @@ msgstr "列" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "描述" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "例子" @@ -9164,7 +9164,7 @@ msgid "Dependencies and requirements" msgstr "install_requires 与 requirements files" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -9366,45 +9366,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "完整示例" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12838,7 +12868,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12847,11 +12877,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "" @@ -12973,15 +13003,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "" @@ -13080,16 +13110,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "例子::" @@ -13280,94 +13310,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "维护者" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -13375,7 +13386,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -13385,33 +13396,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -13419,50 +13430,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -13470,64 +13481,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -13535,13 +13546,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -13549,36 +13560,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13587,13 +13606,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13601,20 +13620,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13622,7 +13641,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13632,11 +13651,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13644,7 +13663,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13654,18 +13673,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13674,7 +13693,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13685,64 +13704,89 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 #, fuzzy msgid "Requires" msgstr "要求" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13753,33 +13797,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13788,89 +13832,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "reStructuredText 标记：https://docutils.sourceforge.io/" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16797,7 +16841,7 @@ msgid "``dependencies``" msgstr "``dependencies``" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -17049,24 +17093,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -17074,14 +17119,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -17089,7 +17134,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -17097,24 +17142,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -17122,7 +17167,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -17133,17 +17178,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -17151,19 +17196,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -17172,20 +17217,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -17193,18 +17238,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -17212,7 +17257,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -17220,14 +17265,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -19274,7 +19319,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19611,30 +19656,30 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 #, fuzzy msgid "Pre-releases" msgstr "zest.releaser" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19642,49 +19687,49 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 #, fuzzy msgid "Post-releases" msgstr "zest.releaser" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19692,7 +19737,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19700,11 +19745,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19712,11 +19757,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19724,20 +19769,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19746,13 +19791,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19762,29 +19807,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "版本" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19795,18 +19840,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "规范化" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19814,23 +19859,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "规范化" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19839,11 +19884,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19853,11 +19898,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19867,11 +19912,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19879,11 +19924,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19894,11 +19939,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19906,11 +19951,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19918,11 +19963,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19932,11 +19977,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19944,11 +19989,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19956,12 +20001,12 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 #, fuzzy msgid "Local version segments" msgstr "本地版本标识符" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19969,11 +20014,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19982,11 +20027,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19995,11 +20040,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -20009,7 +20054,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -20017,69 +20062,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -20087,48 +20132,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -20139,7 +20184,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -20149,17 +20194,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -20168,14 +20213,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -20186,7 +20231,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -20194,30 +20239,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -20225,30 +20270,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -20256,60 +20301,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -20318,80 +20363,80 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 #, fuzzy msgid "Version matching" msgstr "版本" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -20400,7 +20445,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -20408,7 +20453,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -20418,21 +20463,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -20440,7 +20485,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -20449,7 +20494,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -20459,14 +20504,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -20475,29 +20520,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "版本说明符 (Version Specifier)" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -20506,27 +20551,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -20536,7 +20581,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -20546,13 +20591,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20775,7 +20820,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20783,7 +20828,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20794,15 +20839,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "远程 URL 示例::" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20810,7 +20855,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20818,7 +20863,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20830,43 +20875,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20875,20 +20920,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20966,6 +21011,318 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +msgid "Well-known Project URLs in Metadata" +msgstr "项目名称" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "规范化" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "规范化" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +#, fuzzy +#| msgid "Creating documentation" +msgid "``documentation`` (Documentation)" +msgstr "创建文档" + +#: ../source/specifications/well-known-project-urls.rst:124 +#, fuzzy +#| msgid "Creating documentation" +msgid "The project's online documentation" +msgstr "创建文档" + +#: ../source/specifications/well-known-project-urls.rst:125 +#, fuzzy +#| msgid "``upload_docs``" +msgid "``docs``" +msgstr "``upload_docs``" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +#, fuzzy +msgid "Funding Information" +msgstr "附加工具" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +#, fuzzy +#| msgid "Example" +msgid "Example behavior" +msgstr "例子" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "如何获得支持" diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po index 364d1cfd7..a9a4c5efb 100644 --- a/locales/zh_Hant/LC_MESSAGES/messages.po +++ b/locales/zh_Hant/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: 2024-10-15 11:23+0000\n" +"POT-Creation-Date: 2024-10-30 00:39+0000\n" "PO-Revision-Date: 2024-07-03 11:26+0000\n" "Last-Translator: Ricky From Hong Kong \n" "Language-Team: Chinese (Traditional) `), " -"the ``__version__`` attribute should either only be queried with interfaces " -"that are known to provide it (such as a project querying its own version or " -"the version of one of its direct dependencies), or else the querying code " -"should be designed to handle the case where the attribute is missing " -"[#fallback-to-dist-version]_." +"information in this way (see the withdrawn proposal in :pep:`PEP 396 " +"<396>`), the ``__version__`` attribute should either only be queried with " +"interfaces that are known to provide it (such as a project querying its own " +"version or the version of one of its direct dependencies), or else the " +"querying code should be designed to handle the case where the attribute is " +"missing [#fallback-to-dist-version]_." msgstr "" #: ../source/discussions/versioning.rst:210 msgid "" "Some projects may need to publish version information for external APIs that " -"don't meet the requirements for Python distribution package :ref:`version " -"specifiers `. Such projects should define their own " -"project-specific ways of obtaining the relevant information at runtime. For " -"example, the standard library's :mod:`ssl` module offers multiple ways to " -"access the underlying OpenSSL library version::" +"aren't the version of the module itself. Such projects should define their " +"own project-specific ways of obtaining the relevant information at runtime. " +"For example, the standard library's :mod:`ssl` module offers multiple ways " +"to access the underlying OpenSSL library version::" msgstr "" -#: ../source/discussions/versioning.rst:226 +#: ../source/discussions/versioning.rst:225 msgid "" "Some more examples of unusual version numbers are given in a `blog post " "`_ by Seth Larson." msgstr "" -#: ../source/discussions/versioning.rst:229 +#: ../source/discussions/versioning.rst:228 msgid "" "For some personal viewpoints on this issue, see these blog posts: `by Hynek " "Schlawak `_, `by Donald Stufft `_. For a humoristic take, read about ZeroVer_." msgstr "" -#: ../source/discussions/versioning.rst:235 +#: ../source/discussions/versioning.rst:234 msgid "" "A full list mapping the top level names available for import to the " "distribution packages that provide those import packages and modules may be " @@ -3223,13 +3222,14 @@ msgstr "欄" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/core-metadata.rst:194 +#: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" msgstr "描述" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 #: ../source/specifications/direct-url-data-structure.rst:347 -#: ../source/specifications/version-specifiers.rst:1067 +#: ../source/specifications/version-specifiers.rst:1069 msgid "Examples" msgstr "例子" @@ -8747,7 +8747,7 @@ msgid "Dependencies and requirements" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:174 -#: ../source/specifications/pyproject-toml.rst:355 +#: ../source/specifications/pyproject-toml.rst:356 msgid "``dependencies``/``optional-dependencies``" msgstr "" @@ -8947,45 +8947,75 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:404 +#: ../source/guides/writing-pyproject-toml.rst:405 #: ../source/specifications/pyproject-toml.rst:147 #: ../source/specifications/pyproject-toml.rst:314 msgid "``urls``" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:406 +#: ../source/guides/writing-pyproject-toml.rst:407 msgid "" "A list of URLs associated with your project, displayed on the left sidebar " "of your PyPI project page." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:418 +#: ../source/guides/writing-pyproject-toml.rst:412 +msgid "" +"See :ref:`well-known-labels` for a listing of labels that PyPI and other " +"packaging tools are specifically aware of, and `PyPI's project metadata docs " +"`_ for PyPI-specific " +"URL processing." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:426 +msgid "" +"Note that if the label contains spaces, it needs to be quoted, e.g., " +"``Website = \"https://example.com\"`` but ``\"Official Website\" = \"https://" +"example.com\"``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:430 +msgid "" +"Users are advised to use :ref:`well-known-labels` for their project URLs " +"where appropriate, since consumers of metadata (like package indices) can " +"specialize their presentation." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:434 +msgid "" +"For example in the following metadata, neither ``MyHomepage`` nor " +"``\"Download Link\"`` is a well-known label, so they will be rendered " +"verbatim:" +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:444 msgid "" -"Note that if the key contains spaces, it needs to be quoted, e.g., ``Website " -"= \"https://example.com\"`` but ``\"Official Website\" = \"https://example." -"com\"``." +"Whereas in this metadata ``HomePage`` and ``DOWNLOAD`` both have well-known " +"equivalents (``homepage`` and ``download``), and can be presented with those " +"semantics in mind (the project's home page and its external download " +"location, respectively)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:425 +#: ../source/guides/writing-pyproject-toml.rst:456 msgid "Advanced plugins" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:427 +#: ../source/guides/writing-pyproject-toml.rst:458 msgid "" "Some packages can be extended through plugins. Examples include Pytest_ and " "Pygments_. To create such a plugin, you need to declare it in a subtable of " "``[project.entry-points]`` like this:" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:436 +#: ../source/guides/writing-pyproject-toml.rst:467 msgid "See the :ref:`Plugin guide ` for more information." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:441 +#: ../source/guides/writing-pyproject-toml.rst:472 msgid "A full example" msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:503 +#: ../source/guides/writing-pyproject-toml.rst:534 msgid "" "Think twice before applying an upper bound like ``requires-python = \"<= " "3.10\"`` here. `This blog post `_ contains some " @@ -12266,7 +12296,7 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:421 -#: ../source/specifications/core-metadata.rst:905 +#: ../source/specifications/core-metadata.rst:917 #: ../source/specifications/dependency-specifiers.rst:477 #: ../source/specifications/direct-url-data-structure.rst:397 #: ../source/specifications/direct-url.rst:67 @@ -12275,11 +12305,11 @@ msgstr "" #: ../source/specifications/inline-script-metadata.rst:213 #: ../source/specifications/name-normalization.rst:50 #: ../source/specifications/platform-compatibility-tags.rst:332 -#: ../source/specifications/pyproject-toml.rst:443 +#: ../source/specifications/pyproject-toml.rst:444 #: ../source/specifications/recording-installed-packages.rst:252 #: ../source/specifications/simple-repository-api.rst:974 #: ../source/specifications/source-distribution-format.rst:144 -#: ../source/specifications/version-specifiers.rst:1264 +#: ../source/specifications/version-specifiers.rst:1266 #: ../source/specifications/virtual-environments.rst:54 msgid "History" msgstr "歷史" @@ -12401,15 +12431,15 @@ msgstr "" #: ../source/specifications/core-metadata.rst:297 #: ../source/specifications/core-metadata.rst:301 #: ../source/specifications/core-metadata.rst:333 -#: ../source/specifications/core-metadata.rst:354 -#: ../source/specifications/core-metadata.rst:381 -#: ../source/specifications/core-metadata.rst:399 -#: ../source/specifications/core-metadata.rst:424 -#: ../source/specifications/core-metadata.rst:446 -#: ../source/specifications/core-metadata.rst:666 -#: ../source/specifications/core-metadata.rst:697 -#: ../source/specifications/core-metadata.rst:707 -#: ../source/specifications/core-metadata.rst:899 +#: ../source/specifications/core-metadata.rst:355 +#: ../source/specifications/core-metadata.rst:373 +#: ../source/specifications/core-metadata.rst:398 +#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:640 +#: ../source/specifications/core-metadata.rst:675 +#: ../source/specifications/core-metadata.rst:685 +#: ../source/specifications/core-metadata.rst:814 +#: ../source/specifications/core-metadata.rst:911 msgid "Example::" msgstr "例子::" @@ -12508,16 +12538,16 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:147 -#: ../source/specifications/core-metadata.rst:479 -#: ../source/specifications/core-metadata.rst:500 -#: ../source/specifications/core-metadata.rst:523 -#: ../source/specifications/core-metadata.rst:552 -#: ../source/specifications/core-metadata.rst:593 -#: ../source/specifications/core-metadata.rst:649 -#: ../source/specifications/core-metadata.rst:782 -#: ../source/specifications/core-metadata.rst:812 -#: ../source/specifications/core-metadata.rst:853 -#: ../source/specifications/core-metadata.rst:875 +#: ../source/specifications/core-metadata.rst:453 +#: ../source/specifications/core-metadata.rst:474 +#: ../source/specifications/core-metadata.rst:497 +#: ../source/specifications/core-metadata.rst:526 +#: ../source/specifications/core-metadata.rst:567 +#: ../source/specifications/core-metadata.rst:623 +#: ../source/specifications/core-metadata.rst:760 +#: ../source/specifications/core-metadata.rst:790 +#: ../source/specifications/core-metadata.rst:865 +#: ../source/specifications/core-metadata.rst:887 msgid "Examples::" msgstr "例子::" @@ -12708,94 +12738,75 @@ msgid "" msgstr "" #: ../source/specifications/core-metadata.rst:348 -msgid "Home-page" -msgstr "" - -#: ../source/specifications/core-metadata.rst:352 -msgid "A string containing the URL for the distribution's home page." -msgstr "" - -#: ../source/specifications/core-metadata.rst:361 -msgid "Download-URL" -msgstr "" - -#: ../source/specifications/core-metadata.rst:365 -msgid "" -"A string containing the URL from which this version of the distribution can " -"be downloaded. (This means that the URL can't be something like \".../" -"BeagleVote-latest.tgz\", but instead must be \".../BeagleVote-0.45.tgz\".)" -msgstr "" - -#: ../source/specifications/core-metadata.rst:374 msgid "Author" msgstr "作者" -#: ../source/specifications/core-metadata.rst:378 +#: ../source/specifications/core-metadata.rst:352 msgid "" "A string containing the author's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:391 +#: ../source/specifications/core-metadata.rst:365 msgid "Author-email" msgstr "" -#: ../source/specifications/core-metadata.rst:395 +#: ../source/specifications/core-metadata.rst:369 msgid "" "A string containing the author's e-mail address. It can contain a name and " "e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:403 -#: ../source/specifications/core-metadata.rst:450 +#: ../source/specifications/core-metadata.rst:377 +#: ../source/specifications/core-metadata.rst:424 msgid "" "Per RFC-822, this field may contain multiple comma-separated e-mail " "addresses::" msgstr "" -#: ../source/specifications/core-metadata.rst:413 +#: ../source/specifications/core-metadata.rst:387 msgid "Maintainer" msgstr "維護者" -#: ../source/specifications/core-metadata.rst:417 +#: ../source/specifications/core-metadata.rst:391 msgid "" "A string containing the maintainer's name at a minimum; additional contact " "information may be provided." msgstr "" -#: ../source/specifications/core-metadata.rst:420 +#: ../source/specifications/core-metadata.rst:394 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author``." msgstr "" -#: ../source/specifications/core-metadata.rst:434 +#: ../source/specifications/core-metadata.rst:408 msgid "Maintainer-email" msgstr "" -#: ../source/specifications/core-metadata.rst:438 +#: ../source/specifications/core-metadata.rst:412 msgid "" "A string containing the maintainer's e-mail address. It can contain a name " "and e-mail address in the legal forms for a RFC-822 ``From:`` header." msgstr "" -#: ../source/specifications/core-metadata.rst:442 +#: ../source/specifications/core-metadata.rst:416 msgid "" "Note that this field is intended for use when a project is being maintained " "by someone other than the original author: it should be omitted if it is " "identical to ``Author-email``." msgstr "" -#: ../source/specifications/core-metadata.rst:460 +#: ../source/specifications/core-metadata.rst:434 msgid "License" msgstr "許可證" -#: ../source/specifications/core-metadata.rst:463 +#: ../source/specifications/core-metadata.rst:437 msgid "in favour of ``License-Expression``." msgstr "" -#: ../source/specifications/core-metadata.rst:467 +#: ../source/specifications/core-metadata.rst:441 msgid "" "As of Metadata 2.4, ``License`` and ``License-Expression`` are mutually " "exclusive. If both are specified, tools which parse metadata will disregard " @@ -12803,7 +12814,7 @@ msgid "" "org/pep-0639/#deprecate-license-field>`__." msgstr "" -#: ../source/specifications/core-metadata.rst:472 +#: ../source/specifications/core-metadata.rst:446 msgid "" "Text indicating the license covering the distribution where the license is " "not a selection from the \"License\" Trove classifiers. See :ref:" @@ -12813,33 +12824,33 @@ msgid "" "license." msgstr "" -#: ../source/specifications/core-metadata.rst:492 +#: ../source/specifications/core-metadata.rst:466 msgid "License-Expression" msgstr "" -#: ../source/specifications/core-metadata.rst:496 +#: ../source/specifications/core-metadata.rst:470 msgid "" "Text string that is a valid SPDX `license expression `__ as `defined in PEP 639 `__." msgstr "" -#: ../source/specifications/core-metadata.rst:515 +#: ../source/specifications/core-metadata.rst:489 msgid "License-File (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:519 +#: ../source/specifications/core-metadata.rst:493 msgid "" "Each entry is a string representation of the path of a license-related file. " "The path is located within the project source tree, relative to the project " "root directory. For details see :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:536 +#: ../source/specifications/core-metadata.rst:510 msgid "Classifier (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:540 +#: ../source/specifications/core-metadata.rst:514 msgid "" "Each entry is a string giving a single classification value for the " "distribution. Classifiers are described in :pep:`301`, and the Python " @@ -12847,50 +12858,50 @@ msgid "" "`__." msgstr "" -#: ../source/specifications/core-metadata.rst:546 +#: ../source/specifications/core-metadata.rst:520 msgid "" "The use of ``License ::`` classifiers is deprecated as of Metadata 2.4, use " "``License-Expression`` instead. See `PEP 639 `_." msgstr "" -#: ../source/specifications/core-metadata.rst:550 -#: ../source/specifications/core-metadata.rst:640 -#: ../source/specifications/core-metadata.rst:780 -#: ../source/specifications/core-metadata.rst:805 +#: ../source/specifications/core-metadata.rst:524 +#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:758 +#: ../source/specifications/core-metadata.rst:783 msgid "This field may be followed by an environment marker after a semicolon." msgstr "" -#: ../source/specifications/core-metadata.rst:561 +#: ../source/specifications/core-metadata.rst:535 msgid "Requires-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:564 -#: ../source/specifications/core-metadata.rst:627 -#: ../source/specifications/core-metadata.rst:752 -#: ../source/specifications/core-metadata.rst:794 +#: ../source/specifications/core-metadata.rst:538 +#: ../source/specifications/core-metadata.rst:601 +#: ../source/specifications/core-metadata.rst:730 +#: ../source/specifications/core-metadata.rst:772 msgid "" "The field format specification was relaxed to accept the syntax used by " "popular publishing tools." msgstr "" -#: ../source/specifications/core-metadata.rst:568 +#: ../source/specifications/core-metadata.rst:542 msgid "" "Each entry contains a string naming some other distutils project required by " "this distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:571 +#: ../source/specifications/core-metadata.rst:545 msgid "The format of a requirement string contains from one to four parts:" msgstr "" -#: ../source/specifications/core-metadata.rst:573 +#: ../source/specifications/core-metadata.rst:547 msgid "" "A project name, in the same format as the ``Name:`` field. The only " "mandatory part." msgstr "" -#: ../source/specifications/core-metadata.rst:575 +#: ../source/specifications/core-metadata.rst:549 msgid "" "A comma-separated list of 'extra' names. These are defined by the required " "project, referring to specific features which may need extra dependencies. " @@ -12898,64 +12909,64 @@ msgid "" "`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:579 +#: ../source/specifications/core-metadata.rst:553 msgid "" "A version specifier. Tools parsing the format should accept optional " "parentheses around this, but tools generating it should not use parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:582 +#: ../source/specifications/core-metadata.rst:556 msgid "" "An environment marker after a semicolon. This means that the requirement is " "only needed in the specified conditions." msgstr "" -#: ../source/specifications/core-metadata.rst:585 +#: ../source/specifications/core-metadata.rst:559 msgid "See :pep:`508` for full details of the allowed format." msgstr "" -#: ../source/specifications/core-metadata.rst:587 +#: ../source/specifications/core-metadata.rst:561 msgid "" "The project names should correspond to names as found on the `Python Package " "Index`_." msgstr "" -#: ../source/specifications/core-metadata.rst:590 +#: ../source/specifications/core-metadata.rst:564 msgid "" "Version specifiers must follow the rules described in :doc:`version-" "specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:604 +#: ../source/specifications/core-metadata.rst:578 msgid "Requires-Python" msgstr "" -#: ../source/specifications/core-metadata.rst:608 +#: ../source/specifications/core-metadata.rst:582 msgid "" "This field specifies the Python version(s) that the distribution is " "compatible with. Installation tools may look at this when picking which " "version of a project to install." msgstr "" -#: ../source/specifications/core-metadata.rst:612 +#: ../source/specifications/core-metadata.rst:586 msgid "The value must be in the format specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:614 +#: ../source/specifications/core-metadata.rst:588 msgid "" "For example, if a distribution uses :ref:`f-strings ` " "then it may prevent installation on Python < 3.6 by specifying::" msgstr "" -#: ../source/specifications/core-metadata.rst:619 +#: ../source/specifications/core-metadata.rst:593 msgid "This field cannot be followed by an environment marker." msgstr "" -#: ../source/specifications/core-metadata.rst:624 +#: ../source/specifications/core-metadata.rst:598 msgid "Requires-External (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:631 +#: ../source/specifications/core-metadata.rst:605 msgid "" "Each entry contains a string describing some dependency in the system that " "the distribution is to be used. This field is intended to serve as a hint " @@ -12963,13 +12974,13 @@ msgid "" "to the ``distutils`` distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:636 +#: ../source/specifications/core-metadata.rst:610 msgid "" "The format of a requirement string is a name of an external dependency, " "optionally followed by a version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:642 +#: ../source/specifications/core-metadata.rst:616 msgid "" "Because they refer to non-Python software releases, version numbers for this " "field are **not** required to conform to the format specified in the :ref:" @@ -12977,36 +12988,44 @@ msgid "" "correspond to the version scheme used by the external dependency." msgstr "" -#: ../source/specifications/core-metadata.rst:647 +#: ../source/specifications/core-metadata.rst:621 msgid "Notice that there is no particular rule on the strings to be used." msgstr "" -#: ../source/specifications/core-metadata.rst:659 +#: ../source/specifications/core-metadata.rst:633 msgid "Project-URL (multiple-use)" msgstr "" -#: ../source/specifications/core-metadata.rst:663 +#: ../source/specifications/core-metadata.rst:637 msgid "" "A string containing a browsable URL for the project and a label for it, " "separated by a comma." msgstr "" -#: ../source/specifications/core-metadata.rst:670 +#: ../source/specifications/core-metadata.rst:644 msgid "The label is free text limited to 32 characters." msgstr "" -#: ../source/specifications/core-metadata.rst:678 +#: ../source/specifications/core-metadata.rst:646 +msgid "" +"Starting with :pep:`753`, project metadata consumers (such as the Python " +"Package Index) can use a standard normalization process to discover \"well-" +"known\" labels, which can then be given special presentations when being " +"rendered for human consumption. See :ref:`well-known-project-urls`." +msgstr "" + +#: ../source/specifications/core-metadata.rst:656 msgid "Provides-Extra (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:681 +#: ../source/specifications/core-metadata.rst:659 msgid "" ":pep:`685` restricted valid values to be unambiguous (i.e. no normalization " "required). For older metadata versions, value restrictions were brought into " "line with ``Name:`` and normalization rules were introduced." msgstr "" -#: ../source/specifications/core-metadata.rst:686 +#: ../source/specifications/core-metadata.rst:664 msgid "" "A string containing the name of an optional feature. A valid name consists " "only of lowercase ASCII letters, ASCII numbers, and hyphen. It must start " @@ -13015,13 +13034,13 @@ msgid "" "guarantees unambiguity)::" msgstr "" -#: ../source/specifications/core-metadata.rst:694 +#: ../source/specifications/core-metadata.rst:672 msgid "" "The specified name may be used to make a dependency conditional on whether " "the optional feature has been requested." msgstr "" -#: ../source/specifications/core-metadata.rst:702 +#: ../source/specifications/core-metadata.rst:680 msgid "" "A second distribution requires an optional dependency by placing it inside " "square brackets, and can request multiple features by separating them with a " @@ -13029,20 +13048,20 @@ msgid "" "added to the set of requirements for the distribution." msgstr "" -#: ../source/specifications/core-metadata.rst:712 +#: ../source/specifications/core-metadata.rst:690 msgid "" "Two feature names ``test`` and ``doc`` are reserved to mark dependencies " "that are needed for running automated tests and generating documentation, " "respectively." msgstr "" -#: ../source/specifications/core-metadata.rst:716 +#: ../source/specifications/core-metadata.rst:694 msgid "" "It is legal to specify ``Provides-Extra:`` without referencing it in any " "``Requires-Dist:``." msgstr "" -#: ../source/specifications/core-metadata.rst:719 +#: ../source/specifications/core-metadata.rst:697 msgid "" "When writing data for older metadata versions, names MUST be normalized " "following the same rules used for the ``Name:`` field when performing " @@ -13050,7 +13069,7 @@ msgid "" "Extra:`` entries would clash after being normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:724 +#: ../source/specifications/core-metadata.rst:702 msgid "" "When reading data for older metadata versions, tools SHOULD warn when values " "for this field would be invalid under newer metadata versions. If a value " @@ -13060,11 +13079,11 @@ msgid "" "metadata versions." msgstr "" -#: ../source/specifications/core-metadata.rst:732 +#: ../source/specifications/core-metadata.rst:710 msgid "Rarely Used Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:734 +#: ../source/specifications/core-metadata.rst:712 msgid "" "The fields in this section are currently rarely used, as their design was " "inspired by comparable mechanisms in Linux package management systems, and " @@ -13072,7 +13091,7 @@ msgid "" "open index server such as `PyPI `__." msgstr "" -#: ../source/specifications/core-metadata.rst:739 +#: ../source/specifications/core-metadata.rst:717 msgid "" "As a result, popular installation tools ignore them completely, which in " "turn means there is little incentive for package publishers to set them " @@ -13082,18 +13101,18 @@ msgid "" "package repository." msgstr "" -#: ../source/specifications/core-metadata.rst:749 +#: ../source/specifications/core-metadata.rst:727 msgid "Provides-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:756 +#: ../source/specifications/core-metadata.rst:734 msgid "" "Each entry contains a string naming a Distutils project which is contained " "within this distribution. This field *must* include the project identified " "in the ``Name`` field, followed by the version : Name (Version)." msgstr "" -#: ../source/specifications/core-metadata.rst:761 +#: ../source/specifications/core-metadata.rst:739 msgid "" "A distribution may provide additional names, e.g. to indicate that multiple " "projects have been bundled together. For instance, source distributions of " @@ -13102,7 +13121,7 @@ msgid "" "distribution satisfies requirements for both ``ZODB`` and ``transaction``." msgstr "" -#: ../source/specifications/core-metadata.rst:768 +#: ../source/specifications/core-metadata.rst:746 msgid "" "A distribution may also provide a \"virtual\" project name, which does not " "correspond to any separately-distributed project: such a name might be used " @@ -13113,63 +13132,88 @@ msgid "" "them installed." msgstr "" -#: ../source/specifications/core-metadata.rst:776 +#: ../source/specifications/core-metadata.rst:754 msgid "" "A version declaration may be supplied and must follow the rules described " "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:791 +#: ../source/specifications/core-metadata.rst:769 msgid "Obsoletes-Dist (multiple use)" msgstr "" -#: ../source/specifications/core-metadata.rst:798 +#: ../source/specifications/core-metadata.rst:776 msgid "" "Each entry contains a string describing a distutils project's distribution " "which this distribution renders obsolete, meaning that the two projects " "should not be installed at the same time." msgstr "" -#: ../source/specifications/core-metadata.rst:802 +#: ../source/specifications/core-metadata.rst:780 msgid "" "Version declarations can be supplied. Version numbers must be in the format " "specified in :doc:`version-specifiers`." msgstr "" -#: ../source/specifications/core-metadata.rst:807 +#: ../source/specifications/core-metadata.rst:785 msgid "" "The most common use of this field will be in case a project name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon distribution should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:820 +#: ../source/specifications/core-metadata.rst:798 msgid "Deprecated Fields" msgstr "" -#: ../source/specifications/core-metadata.rst:823 +#: ../source/specifications/core-metadata.rst:804 +msgid "Home-page" +msgstr "" + +#: ../source/specifications/core-metadata.rst:810 +#: ../source/specifications/core-metadata.rst:827 +msgid "Per :pep:`753`, use :ref:`core-metadata-project-url` instead." +msgstr "" + +#: ../source/specifications/core-metadata.rst:812 +msgid "A string containing the URL for the distribution's home page." +msgstr "" + +#: ../source/specifications/core-metadata.rst:821 +msgid "Download-URL" +msgstr "" + +#: ../source/specifications/core-metadata.rst:829 +msgid "" +"A string containing the URL from which this version of the distribution can " +"be downloaded. (This means that the URL can't be something like \"``.../" +"BeagleVote-latest.tgz``\", but instead must be \"``.../BeagleVote-0.45." +"tgz``\".)" +msgstr "" + +#: ../source/specifications/core-metadata.rst:835 msgid "Requires" msgstr "需要" -#: ../source/specifications/core-metadata.rst:826 +#: ../source/specifications/core-metadata.rst:838 msgid "in favour of ``Requires-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:829 +#: ../source/specifications/core-metadata.rst:841 msgid "" "Each entry contains a string describing some other module or package " "required by this package." msgstr "" -#: ../source/specifications/core-metadata.rst:832 +#: ../source/specifications/core-metadata.rst:844 msgid "" "The format of a requirement string is identical to that of a module or " "package name usable with the ``import`` statement, optionally followed by a " "version declaration within parentheses." msgstr "" -#: ../source/specifications/core-metadata.rst:836 +#: ../source/specifications/core-metadata.rst:848 msgid "" "A version declaration is a series of conditional operators and version " "numbers, separated by commas. Conditional operators must be one of \"<\", " @@ -13180,33 +13224,33 @@ msgid "" "version numbers are \"1.0\", \"2.3a2\", \"1.3.99\"," msgstr "" -#: ../source/specifications/core-metadata.rst:844 +#: ../source/specifications/core-metadata.rst:856 msgid "" "Any number of conditional operators can be specified, e.g. the string " "\">1.0, !=1.3.4, <2.0\" is a legal version declaration." msgstr "" -#: ../source/specifications/core-metadata.rst:847 +#: ../source/specifications/core-metadata.rst:859 msgid "" "All of the following are possible requirement strings: \"rfc822\", \"zlib " "(>=1.1.4)\", \"zope\"." msgstr "" -#: ../source/specifications/core-metadata.rst:850 +#: ../source/specifications/core-metadata.rst:862 msgid "" "There’s no canonical list of what strings should be used; the Python " "community is left to choose its own standards." msgstr "" -#: ../source/specifications/core-metadata.rst:863 +#: ../source/specifications/core-metadata.rst:875 msgid "Provides" msgstr "提供" -#: ../source/specifications/core-metadata.rst:866 +#: ../source/specifications/core-metadata.rst:878 msgid "in favour of ``Provides-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:869 +#: ../source/specifications/core-metadata.rst:881 msgid "" "Each entry contains a string describing a package or module that will be " "provided by this package once it is installed. These strings should match " @@ -13215,89 +13259,89 @@ msgid "" "implied if none is specified." msgstr "" -#: ../source/specifications/core-metadata.rst:885 +#: ../source/specifications/core-metadata.rst:897 msgid "Obsoletes" msgstr "" -#: ../source/specifications/core-metadata.rst:888 +#: ../source/specifications/core-metadata.rst:900 msgid "in favour of ``Obsoletes-Dist``" msgstr "" -#: ../source/specifications/core-metadata.rst:891 +#: ../source/specifications/core-metadata.rst:903 msgid "" "Each entry contains a string describing a package or module that this " "package renders obsolete, meaning that the two packages should not be " "installed at the same time. Version declarations can be supplied." msgstr "" -#: ../source/specifications/core-metadata.rst:895 +#: ../source/specifications/core-metadata.rst:907 msgid "" "The most common use of this field will be in case a package name changes, e." "g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install " "Torqued Python, the Gorgon package should be removed." msgstr "" -#: ../source/specifications/core-metadata.rst:907 +#: ../source/specifications/core-metadata.rst:919 msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." msgstr "" -#: ../source/specifications/core-metadata.rst:908 +#: ../source/specifications/core-metadata.rst:920 msgid "April 2003: Core metadata 1.1 was approved through :pep:`314`:" msgstr "" -#: ../source/specifications/core-metadata.rst:909 +#: ../source/specifications/core-metadata.rst:921 msgid "February 2010: Core metadata 1.2 was approved through :pep:`345`." msgstr "" -#: ../source/specifications/core-metadata.rst:910 +#: ../source/specifications/core-metadata.rst:922 msgid "February 2018: Core metadata 2.1 was approved through :pep:`566`." msgstr "" -#: ../source/specifications/core-metadata.rst:912 +#: ../source/specifications/core-metadata.rst:924 msgid "Added ``Description-Content-Type`` and ``Provides-Extra``." msgstr "" -#: ../source/specifications/core-metadata.rst:913 +#: ../source/specifications/core-metadata.rst:925 msgid "Added canonical method for transforming metadata to JSON." msgstr "" -#: ../source/specifications/core-metadata.rst:914 +#: ../source/specifications/core-metadata.rst:926 msgid "Restricted the grammar of the ``Name`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:916 +#: ../source/specifications/core-metadata.rst:928 msgid "October 2020: Core metadata 2.2 was approved through :pep:`643`." msgstr "" -#: ../source/specifications/core-metadata.rst:918 +#: ../source/specifications/core-metadata.rst:930 msgid "Added the ``Dynamic`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:920 +#: ../source/specifications/core-metadata.rst:932 msgid "March 2022: Core metadata 2.3 was approved through :pep:`685`." msgstr "" -#: ../source/specifications/core-metadata.rst:922 +#: ../source/specifications/core-metadata.rst:934 msgid "Restricted extra names to be normalized." msgstr "" -#: ../source/specifications/core-metadata.rst:924 +#: ../source/specifications/core-metadata.rst:936 msgid "August 2024: Core metadata 2.4 was approved through :pep:`639`." msgstr "" -#: ../source/specifications/core-metadata.rst:926 +#: ../source/specifications/core-metadata.rst:938 msgid "Added the ``License-Expression`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:927 +#: ../source/specifications/core-metadata.rst:939 msgid "Added the ``License-File`` field." msgstr "" -#: ../source/specifications/core-metadata.rst:931 +#: ../source/specifications/core-metadata.rst:943 msgid "reStructuredText markup: https://docutils.sourceforge.io/" msgstr "" -#: ../source/specifications/core-metadata.rst:936 +#: ../source/specifications/core-metadata.rst:948 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" msgstr "" @@ -16217,7 +16261,7 @@ msgid "``dependencies``" msgstr "" #: ../source/specifications/pyproject-toml.rst:136 -#: ../source/specifications/pyproject-toml.rst:385 +#: ../source/specifications/pyproject-toml.rst:386 msgid "``dynamic``" msgstr "" @@ -16470,24 +16514,25 @@ msgstr "" #: ../source/specifications/pyproject-toml.rst:320 msgid "" "A table of URLs where the key is the URL label and the value is the URL " -"itself." +"itself. See :ref:`well-known-project-urls` for normalization rules and well-" +"known rules when processing metadata for presentation." msgstr "" -#: ../source/specifications/pyproject-toml.rst:325 +#: ../source/specifications/pyproject-toml.rst:326 msgid "Entry points" msgstr "" -#: ../source/specifications/pyproject-toml.rst:327 +#: ../source/specifications/pyproject-toml.rst:328 msgid "" "TOML_ type: table (``[project.scripts]``, ``[project.gui-scripts]``, and " "``[project.entry-points]``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:329 +#: ../source/specifications/pyproject-toml.rst:330 msgid ":ref:`Entry points specification `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:331 +#: ../source/specifications/pyproject-toml.rst:332 msgid "" "There are three tables related to entry points. The ``[project.scripts]`` " "table corresponds to the ``console_scripts`` group in the :ref:`entry points " @@ -16495,14 +16540,14 @@ msgid "" "point and the value is the object reference." msgstr "" -#: ../source/specifications/pyproject-toml.rst:337 +#: ../source/specifications/pyproject-toml.rst:338 msgid "" "The ``[project.gui-scripts]`` table corresponds to the ``gui_scripts`` group " "in the :ref:`entry points specification `. Its format is the " "same as ``[project.scripts]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:341 +#: ../source/specifications/pyproject-toml.rst:342 msgid "" "The ``[project.entry-points]`` table is a collection of tables. Each sub-" "table's name is an entry point group. The key and value semantics are the " @@ -16510,7 +16555,7 @@ msgid "" "instead keep the entry point groups to only one level deep." msgstr "" -#: ../source/specifications/pyproject-toml.rst:347 +#: ../source/specifications/pyproject-toml.rst:348 msgid "" "Build back-ends MUST raise an error if the metadata defines a ``[project." "entry-points.console_scripts]`` or ``[project.entry-points.gui_scripts]`` " @@ -16518,24 +16563,24 @@ msgid "" "``[project.gui-scripts]``, respectively." msgstr "" -#: ../source/specifications/pyproject-toml.rst:357 +#: ../source/specifications/pyproject-toml.rst:358 msgid "" "TOML_ type: Array of :pep:`508` strings (``dependencies``), and a table with " "values of arrays of :pep:`508` strings (``optional-dependencies``)" msgstr "" -#: ../source/specifications/pyproject-toml.rst:360 +#: ../source/specifications/pyproject-toml.rst:361 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Requires-" "Dist ` and :ref:`Provides-Extra `" msgstr "" -#: ../source/specifications/pyproject-toml.rst:364 +#: ../source/specifications/pyproject-toml.rst:365 msgid "The (optional) dependencies of the project." msgstr "" -#: ../source/specifications/pyproject-toml.rst:366 +#: ../source/specifications/pyproject-toml.rst:367 msgid "" "For ``dependencies``, it is a key whose value is an array of strings. Each " "string represents a dependency of the project and MUST be formatted as a " @@ -16543,7 +16588,7 @@ msgid "" "` entry." msgstr "" -#: ../source/specifications/pyproject-toml.rst:371 +#: ../source/specifications/pyproject-toml.rst:372 msgid "" "For ``optional-dependencies``, it is a table where each key specifies an " "extra and whose value is an array of strings. The strings of the arrays must " @@ -16554,17 +16599,17 @@ msgid "" "extra>` metadata." msgstr "" -#: ../source/specifications/pyproject-toml.rst:387 +#: ../source/specifications/pyproject-toml.rst:388 msgid "TOML_ type: array of string" msgstr "" -#: ../source/specifications/pyproject-toml.rst:388 +#: ../source/specifications/pyproject-toml.rst:389 msgid "" "Corresponding :ref:`core metadata ` field: :ref:`Dynamic " "`" msgstr "" -#: ../source/specifications/pyproject-toml.rst:391 +#: ../source/specifications/pyproject-toml.rst:392 msgid "" "Specifies which keys listed by this PEP were intentionally unspecified so " "another tool can/will provide such metadata dynamically. This clearly " @@ -16572,19 +16617,19 @@ msgid "" "unspecified compared to being provided via tooling later on." msgstr "" -#: ../source/specifications/pyproject-toml.rst:397 +#: ../source/specifications/pyproject-toml.rst:398 msgid "" "A build back-end MUST honour statically-specified metadata (which means the " "metadata did not list the key in ``dynamic``)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:399 +#: ../source/specifications/pyproject-toml.rst:400 msgid "" "A build back-end MUST raise an error if the metadata specifies ``name`` in " "``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:401 +#: ../source/specifications/pyproject-toml.rst:402 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Required\", then the metadata MUST specify the key statically or list it " @@ -16593,20 +16638,20 @@ msgid "" "``[project]`` table)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:406 +#: ../source/specifications/pyproject-toml.rst:407 msgid "" "If the :ref:`core metadata ` specification lists a field as " "\"Optional\", the metadata MAY list it in ``dynamic`` if the expectation is " "a build back-end will provide the data for the key later." msgstr "" -#: ../source/specifications/pyproject-toml.rst:410 +#: ../source/specifications/pyproject-toml.rst:411 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key " "statically as well as being listed in ``dynamic``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:412 +#: ../source/specifications/pyproject-toml.rst:413 msgid "" "If the metadata does not list a key in ``dynamic``, then a build back-end " "CANNOT fill in the requisite metadata on behalf of the user (i.e. " @@ -16614,18 +16659,18 @@ msgid "" "must opt into the filling in)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:416 +#: ../source/specifications/pyproject-toml.rst:417 msgid "" "Build back-ends MUST raise an error if the metadata specifies a key in " "``dynamic`` but the build back-end was unable to determine the data for it " "(omitting the data, if determined to be the accurate value, is acceptable)." msgstr "" -#: ../source/specifications/pyproject-toml.rst:426 +#: ../source/specifications/pyproject-toml.rst:427 msgid "Arbitrary tool configuration: the ``[tool]`` table" msgstr "" -#: ../source/specifications/pyproject-toml.rst:428 +#: ../source/specifications/pyproject-toml.rst:429 msgid "" "The ``[tool]`` table is where any tool related to your Python project, not " "just build tools, can have users specify configuration data as long as they " @@ -16633,7 +16678,7 @@ msgid "" "pypi/flit>`_ tool would store its configuration in ``[tool.flit]``." msgstr "" -#: ../source/specifications/pyproject-toml.rst:434 +#: ../source/specifications/pyproject-toml.rst:435 msgid "" "A mechanism is needed to allocate names within the ``tool.*`` namespace, to " "make sure that different projects do not attempt to use the same sub-table " @@ -16641,14 +16686,14 @@ msgid "" "if, and only if, they own the entry for ``$NAME`` in the Cheeseshop/PyPI." msgstr "" -#: ../source/specifications/pyproject-toml.rst:445 +#: ../source/specifications/pyproject-toml.rst:446 msgid "" "May 2016: The initial specification of the ``pyproject.toml`` file, with " "just a ``[build-system]`` containing a ``requires`` key and a ``[tool]`` " "table, was approved through :pep:`518`." msgstr "" -#: ../source/specifications/pyproject-toml.rst:449 +#: ../source/specifications/pyproject-toml.rst:450 msgid "" "November 2020: The specification of the ``[project]`` table was approved " "through :pep:`621`." @@ -18696,7 +18741,7 @@ msgid "" msgstr "" #: ../source/specifications/version-specifiers.rst:7 -#: ../source/specifications/version-specifiers.rst:780 +#: ../source/specifications/version-specifiers.rst:782 msgid "Version specifiers" msgstr "" @@ -19030,29 +19075,29 @@ msgid "" "release scheme using the year and month of the release::" msgstr "" -#: ../source/specifications/version-specifiers.rst:241 +#: ../source/specifications/version-specifiers.rst:243 msgid "Pre-releases" msgstr "預發行" -#: ../source/specifications/version-specifiers.rst:243 +#: ../source/specifications/version-specifiers.rst:245 msgid "" "Some projects use an \"alpha, beta, release candidate\" pre-release cycle to " "support testing by their users prior to a final release." msgstr "" -#: ../source/specifications/version-specifiers.rst:246 +#: ../source/specifications/version-specifiers.rst:248 msgid "" "If used as part of a project's development cycle, these pre-releases are " "indicated by including a pre-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:254 +#: ../source/specifications/version-specifiers.rst:256 msgid "" "A version identifier that consists solely of a release segment and a pre-" "release segment is termed a \"pre-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:257 +#: ../source/specifications/version-specifiers.rst:259 msgid "" "The pre-release segment consists of an alphabetical identifier for the pre-" "release phase, along with a non-negative integer value. Pre-releases for a " @@ -19060,48 +19105,48 @@ msgid "" "and then by the numerical component within that phase." msgstr "" -#: ../source/specifications/version-specifiers.rst:262 +#: ../source/specifications/version-specifiers.rst:264 msgid "" "Installation tools MAY accept both ``c`` and ``rc`` releases for a common " "release segment in order to handle some existing legacy distributions." msgstr "" -#: ../source/specifications/version-specifiers.rst:265 +#: ../source/specifications/version-specifiers.rst:267 msgid "" "Installation tools SHOULD interpret ``c`` versions as being equivalent to " "``rc`` versions (that is, ``c1`` indicates the same version as ``rc1``)." msgstr "" -#: ../source/specifications/version-specifiers.rst:268 +#: ../source/specifications/version-specifiers.rst:270 msgid "" "Build tools, publication tools and index servers SHOULD disallow the " "creation of both ``rc`` and ``c`` releases for a common release segment." msgstr "" -#: ../source/specifications/version-specifiers.rst:273 +#: ../source/specifications/version-specifiers.rst:275 msgid "Post-releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:275 +#: ../source/specifications/version-specifiers.rst:277 msgid "" "Some projects use post-releases to address minor errors in a final release " "that do not affect the distributed software (for example, correcting an " "error in the release notes)." msgstr "" -#: ../source/specifications/version-specifiers.rst:279 +#: ../source/specifications/version-specifiers.rst:281 msgid "" "If used as part of a project's development cycle, these post-releases are " "indicated by including a post-release segment in the version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:284 +#: ../source/specifications/version-specifiers.rst:286 msgid "" "A version identifier that includes a post-release segment without a " "developmental release segment is termed a \"post-release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:287 +#: ../source/specifications/version-specifiers.rst:289 msgid "" "The post-release segment consists of the string ``.post``, followed by a non-" "negative integer value. Post-releases are ordered by their numerical " @@ -19109,7 +19154,7 @@ msgid "" "subsequent release." msgstr "" -#: ../source/specifications/version-specifiers.rst:294 +#: ../source/specifications/version-specifiers.rst:296 msgid "" "The use of post-releases to publish maintenance releases containing actual " "bug fixes is strongly discouraged. In general, it is better to use a longer " @@ -19117,11 +19162,11 @@ msgid "" "release." msgstr "" -#: ../source/specifications/version-specifiers.rst:299 +#: ../source/specifications/version-specifiers.rst:301 msgid "Post-releases are also permitted for pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:307 +#: ../source/specifications/version-specifiers.rst:309 msgid "" "Creating post-releases of pre-releases is strongly discouraged, as it makes " "the version identifier difficult to parse for human readers. In general, it " @@ -19129,11 +19174,11 @@ msgid "" "the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:314 +#: ../source/specifications/version-specifiers.rst:316 msgid "Developmental releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:316 +#: ../source/specifications/version-specifiers.rst:318 msgid "" "Some projects make regular developmental releases, and system packagers " "(especially for Linux distributions) may wish to create early releases " @@ -19141,20 +19186,20 @@ msgid "" "releases." msgstr "" -#: ../source/specifications/version-specifiers.rst:321 +#: ../source/specifications/version-specifiers.rst:323 msgid "" "If used as part of a project's development cycle, these developmental " "releases are indicated by including a developmental release segment in the " "version identifier::" msgstr "" -#: ../source/specifications/version-specifiers.rst:327 +#: ../source/specifications/version-specifiers.rst:329 msgid "" "A version identifier that includes a developmental release segment is termed " "a \"developmental release\"." msgstr "" -#: ../source/specifications/version-specifiers.rst:330 +#: ../source/specifications/version-specifiers.rst:332 msgid "" "The developmental release segment consists of the string ``.dev``, followed " "by a non-negative integer value. Developmental releases are ordered by their " @@ -19163,13 +19208,13 @@ msgid "" "previous release (including any post-releases)." msgstr "" -#: ../source/specifications/version-specifiers.rst:336 +#: ../source/specifications/version-specifiers.rst:338 msgid "" "Developmental releases are also permitted for pre-releases and post-" "releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:346 +#: ../source/specifications/version-specifiers.rst:348 msgid "" "While they may be useful for continuous integration purposes, publishing " "developmental releases of pre-releases to general purpose public index " @@ -19179,29 +19224,29 @@ msgid "" "by incrementing the numeric component." msgstr "" -#: ../source/specifications/version-specifiers.rst:353 +#: ../source/specifications/version-specifiers.rst:355 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:359 +#: ../source/specifications/version-specifiers.rst:361 #, fuzzy msgid "Version epochs" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:361 +#: ../source/specifications/version-specifiers.rst:363 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:366 +#: ../source/specifications/version-specifiers.rst:368 msgid "If no explicit epoch is given, the implicit epoch is ``0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:368 +#: ../source/specifications/version-specifiers.rst:370 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 " @@ -19212,18 +19257,18 @@ msgid "" "using the normal sorting scheme::" msgstr "" -#: ../source/specifications/version-specifiers.rst:382 +#: ../source/specifications/version-specifiers.rst:384 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:396 +#: ../source/specifications/version-specifiers.rst:398 msgid "Normalization" msgstr "正規化" -#: ../source/specifications/version-specifiers.rst:398 +#: ../source/specifications/version-specifiers.rst:400 msgid "" "In order to maintain better compatibility with existing versions there are a " "number of \"alternative\" syntaxes that MUST be taken into account when " @@ -19231,23 +19276,23 @@ msgid "" "however they should be \"normalized\" to the standard syntax defined above." msgstr "" -#: ../source/specifications/version-specifiers.rst:405 +#: ../source/specifications/version-specifiers.rst:407 msgid "Case sensitivity" msgstr "" -#: ../source/specifications/version-specifiers.rst:407 +#: ../source/specifications/version-specifiers.rst:409 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:413 +#: ../source/specifications/version-specifiers.rst:415 #, fuzzy msgid "Integer Normalization" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:415 +#: ../source/specifications/version-specifiers.rst:417 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`` " @@ -19256,11 +19301,11 @@ msgid "" "version such as ``1.0+foo0100`` which is already in its normalized form." msgstr "" -#: ../source/specifications/version-specifiers.rst:423 +#: ../source/specifications/version-specifiers.rst:425 msgid "Pre-release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:425 +#: ../source/specifications/version-specifiers.rst:427 msgid "" "Pre-releases should allow a ``.``, ``-``, or ``_`` separator between the " "release segment and the pre-release segment. The normal form for this is " @@ -19270,11 +19315,11 @@ msgid "" "versions such as ``1.0a.1`` which would be normalized to ``1.0a1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:434 +#: ../source/specifications/version-specifiers.rst:436 msgid "Pre-release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:436 +#: ../source/specifications/version-specifiers.rst:438 msgid "" "Pre-releases allow the additional spellings of ``alpha``, ``beta``, ``c``, " "``pre``, and ``preview`` for ``a``, ``b``, ``rc``, ``rc``, and ``rc`` " @@ -19284,11 +19329,11 @@ msgid "" "forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:445 +#: ../source/specifications/version-specifiers.rst:447 msgid "Implicit pre-release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:447 +#: ../source/specifications/version-specifiers.rst:449 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`` " @@ -19296,11 +19341,11 @@ msgid "" "``1.2a0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:453 +#: ../source/specifications/version-specifiers.rst:455 msgid "Post release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:455 +#: ../source/specifications/version-specifiers.rst:457 msgid "" "Post releases allow a ``.``, ``-``, or ``_`` separator as well as omitting " "the separator all together. The normal form of this is with the ``.`` " @@ -19311,11 +19356,11 @@ msgid "" "post2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:464 +#: ../source/specifications/version-specifiers.rst:466 msgid "Post release spelling" msgstr "" -#: ../source/specifications/version-specifiers.rst:466 +#: ../source/specifications/version-specifiers.rst:468 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 " @@ -19323,11 +19368,11 @@ msgid "" "equivalent to their normal forms." msgstr "" -#: ../source/specifications/version-specifiers.rst:473 +#: ../source/specifications/version-specifiers.rst:475 msgid "Implicit post release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:475 +#: ../source/specifications/version-specifiers.rst:477 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`` " @@ -19335,11 +19380,11 @@ msgid "" "``1.2.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:481 +#: ../source/specifications/version-specifiers.rst:483 msgid "Implicit post releases" msgstr "" -#: ../source/specifications/version-specifiers.rst:483 +#: ../source/specifications/version-specifiers.rst:485 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 " @@ -19349,11 +19394,11 @@ msgid "" "and it does *not* normalize to ``1.0.post0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:492 +#: ../source/specifications/version-specifiers.rst:494 msgid "Development release separators" msgstr "" -#: ../source/specifications/version-specifiers.rst:494 +#: ../source/specifications/version-specifiers.rst:496 msgid "" "Development releases allow a ``.``, ``-``, or a ``_`` separator as well as " "omitting the separator all together. The normal form of this is with the ``." @@ -19361,11 +19406,11 @@ msgid "" "normalize to ``1.2.dev2``." msgstr "" -#: ../source/specifications/version-specifiers.rst:501 +#: ../source/specifications/version-specifiers.rst:503 msgid "Implicit development release number" msgstr "" -#: ../source/specifications/version-specifiers.rst:503 +#: ../source/specifications/version-specifiers.rst:505 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 " @@ -19373,11 +19418,11 @@ msgid "" "normalized to ``1.2.dev0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:510 +#: ../source/specifications/version-specifiers.rst:512 msgid "Local version segments" msgstr "" -#: ../source/specifications/version-specifiers.rst:512 +#: ../source/specifications/version-specifiers.rst:514 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 " @@ -19385,11 +19430,11 @@ msgid "" "be normalized to ``1.0+ubuntu.1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:519 +#: ../source/specifications/version-specifiers.rst:521 msgid "Preceding v character" msgstr "" -#: ../source/specifications/version-specifiers.rst:521 +#: ../source/specifications/version-specifiers.rst:523 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 " @@ -19398,11 +19443,11 @@ msgid "" "equivalent." msgstr "" -#: ../source/specifications/version-specifiers.rst:528 +#: ../source/specifications/version-specifiers.rst:530 msgid "Leading and Trailing Whitespace" msgstr "" -#: ../source/specifications/version-specifiers.rst:530 +#: ../source/specifications/version-specifiers.rst:532 msgid "" "Leading and trailing whitespace must be silently ignored and removed from " "all normalized forms of a version. This includes ``\" \"``, ``\\t``, " @@ -19411,11 +19456,11 @@ msgid "" "``1.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:537 +#: ../source/specifications/version-specifiers.rst:539 msgid "Examples of compliant version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:539 +#: ../source/specifications/version-specifiers.rst:541 msgid "" "The standard version scheme is designed to encompass a wide range of " "identification practices across public and private Python projects. In " @@ -19425,7 +19470,7 @@ msgid "" "ensure all compliant tools will order them consistently." msgstr "" -#: ../source/specifications/version-specifiers.rst:546 +#: ../source/specifications/version-specifiers.rst:548 msgid "" "The following examples illustrate a small selection of the different " "approaches projects may choose to identify their releases, while still " @@ -19433,69 +19478,69 @@ msgid "" "be easily determined, both by human users and automated tools." msgstr "" -#: ../source/specifications/version-specifiers.rst:551 +#: ../source/specifications/version-specifiers.rst:553 msgid "Simple \"major.minor\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:560 +#: ../source/specifications/version-specifiers.rst:562 msgid "Simple \"major.minor.micro\" versioning::" msgstr "" -#: ../source/specifications/version-specifiers.rst:568 +#: ../source/specifications/version-specifiers.rst:570 msgid "" "\"major.minor\" versioning with alpha, beta and candidate pre-releases::" msgstr "" -#: ../source/specifications/version-specifiers.rst:580 +#: ../source/specifications/version-specifiers.rst:582 msgid "" "\"major.minor\" versioning with developmental releases, release candidates " "and post-releases for minor corrections::" msgstr "" -#: ../source/specifications/version-specifiers.rst:595 +#: ../source/specifications/version-specifiers.rst:597 msgid "" "Date based releases, using an incrementing serial within each year, skipping " "zero::" msgstr "" -#: ../source/specifications/version-specifiers.rst:609 +#: ../source/specifications/version-specifiers.rst:611 msgid "Summary of permitted suffixes and relative ordering" msgstr "" -#: ../source/specifications/version-specifiers.rst:613 +#: ../source/specifications/version-specifiers.rst:615 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:617 +#: ../source/specifications/version-specifiers.rst:619 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:621 +#: ../source/specifications/version-specifiers.rst:623 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:627 +#: ../source/specifications/version-specifiers.rst:629 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:630 +#: ../source/specifications/version-specifiers.rst:632 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:635 +#: ../source/specifications/version-specifiers.rst:637 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 " @@ -19503,48 +19548,48 @@ msgid "" "ambiguous and remain in compliance with the specification." msgstr "" -#: ../source/specifications/version-specifiers.rst:640 +#: ../source/specifications/version-specifiers.rst:642 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:646 +#: ../source/specifications/version-specifiers.rst:648 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:651 +#: ../source/specifications/version-specifiers.rst:653 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:655 +#: ../source/specifications/version-specifiers.rst:657 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:658 +#: ../source/specifications/version-specifiers.rst:660 msgid "The following example covers many of the possible combinations::" msgstr "" -#: ../source/specifications/version-specifiers.rst:683 +#: ../source/specifications/version-specifiers.rst:685 msgid "Version ordering across different metadata versions" msgstr "" -#: ../source/specifications/version-specifiers.rst:685 +#: ../source/specifications/version-specifiers.rst:687 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:689 +#: ../source/specifications/version-specifiers.rst:691 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 " @@ -19555,7 +19600,7 @@ msgid "" "be used for all versions of a project." msgstr "" -#: ../source/specifications/version-specifiers.rst:697 +#: ../source/specifications/version-specifiers.rst:699 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 " @@ -19565,17 +19610,17 @@ msgid "" "available." msgstr "" -#: ../source/specifications/version-specifiers.rst:703 +#: ../source/specifications/version-specifiers.rst:705 msgid "" "Distribution users may wish to explicitly remove non-compliant versions from " "any private package indexes they control." msgstr "" -#: ../source/specifications/version-specifiers.rst:708 +#: ../source/specifications/version-specifiers.rst:710 msgid "Compatibility with other version schemes" msgstr "" -#: ../source/specifications/version-specifiers.rst:710 +#: ../source/specifications/version-specifiers.rst:712 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 " @@ -19584,14 +19629,14 @@ msgid "" "field." msgstr "" -#: ../source/specifications/version-specifiers.rst:715 +#: ../source/specifications/version-specifiers.rst:717 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:723 +#: ../source/specifications/version-specifiers.rst:725 msgid "" "`Semantic versioning`_ is a popular version identification scheme that is " "more prescriptive than this specification regarding the significance of " @@ -19602,7 +19647,7 @@ msgid "" "on." msgstr "" -#: ../source/specifications/version-specifiers.rst:730 +#: ../source/specifications/version-specifiers.rst:732 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 " @@ -19610,30 +19655,30 @@ msgid "" "specification, and abiding by these aspects is encouraged." msgstr "" -#: ../source/specifications/version-specifiers.rst:735 +#: ../source/specifications/version-specifiers.rst:737 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:739 +#: ../source/specifications/version-specifiers.rst:741 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:743 +#: ../source/specifications/version-specifiers.rst:745 msgid "" "Specific build information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:749 +#: ../source/specifications/version-specifiers.rst:751 msgid "DVCS based version labels" msgstr "" -#: ../source/specifications/version-specifiers.rst:751 +#: ../source/specifications/version-specifiers.rst:753 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. " @@ -19641,30 +19686,30 @@ msgid "" "public version field." msgstr "" -#: ../source/specifications/version-specifiers.rst:756 +#: ../source/specifications/version-specifiers.rst:758 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:760 +#: ../source/specifications/version-specifiers.rst:762 msgid "" "Identifying hash information may also be included in local version labels." msgstr "" -#: ../source/specifications/version-specifiers.rst:764 +#: ../source/specifications/version-specifiers.rst:766 msgid "Olson database versioning" msgstr "" -#: ../source/specifications/version-specifiers.rst:766 +#: ../source/specifications/version-specifiers.rst:768 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:770 +#: ../source/specifications/version-specifiers.rst:772 msgid "" "This can be translated to a compliant public version identifier as ``." "``, where the serial starts at zero or one (for the 'a' " @@ -19672,60 +19717,60 @@ msgid "" "year." msgstr "" -#: ../source/specifications/version-specifiers.rst:775 +#: ../source/specifications/version-specifiers.rst:777 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:782 +#: ../source/specifications/version-specifiers.rst:784 msgid "" "A version specifier consists of a series of version clauses, separated by " "commas. For example::" msgstr "" -#: ../source/specifications/version-specifiers.rst:787 +#: ../source/specifications/version-specifiers.rst:789 msgid "The comparison operator determines the kind of version clause:" msgstr "" -#: ../source/specifications/version-specifiers.rst:789 +#: ../source/specifications/version-specifiers.rst:791 msgid "``~=``: `Compatible release`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:790 +#: ../source/specifications/version-specifiers.rst:792 msgid "``==``: `Version matching`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:791 +#: ../source/specifications/version-specifiers.rst:793 msgid "``!=``: `Version exclusion`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:792 +#: ../source/specifications/version-specifiers.rst:794 msgid "``<=``, ``>=``: `Inclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:793 +#: ../source/specifications/version-specifiers.rst:795 msgid "``<``, ``>``: `Exclusive ordered comparison`_ clause" msgstr "" -#: ../source/specifications/version-specifiers.rst:794 +#: ../source/specifications/version-specifiers.rst:796 msgid "``===``: `Arbitrary equality`_ clause." msgstr "" -#: ../source/specifications/version-specifiers.rst:796 +#: ../source/specifications/version-specifiers.rst:798 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:800 +#: ../source/specifications/version-specifiers.rst:802 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:803 +#: ../source/specifications/version-specifiers.rst:805 msgid "" "When multiple candidate versions match a version specifier, the preferred " "version SHOULD be the latest version as determined by the consistent " @@ -19734,79 +19779,79 @@ msgid "" "in `Handling of pre-releases`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:809 +#: ../source/specifications/version-specifiers.rst:811 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:818 +#: ../source/specifications/version-specifiers.rst:820 msgid "Compatible release" msgstr "" -#: ../source/specifications/version-specifiers.rst:820 +#: ../source/specifications/version-specifiers.rst:822 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:824 +#: ../source/specifications/version-specifiers.rst:826 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:828 +#: ../source/specifications/version-specifiers.rst:830 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:833 +#: ../source/specifications/version-specifiers.rst:835 msgid "" "This operator MUST NOT be used with a single segment version number such as " "``~=1``." msgstr "" -#: ../source/specifications/version-specifiers.rst:836 +#: ../source/specifications/version-specifiers.rst:838 msgid "For example, the following groups of version clauses are equivalent::" msgstr "" -#: ../source/specifications/version-specifiers.rst:844 +#: ../source/specifications/version-specifiers.rst:846 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:854 +#: ../source/specifications/version-specifiers.rst:856 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:866 +#: ../source/specifications/version-specifiers.rst:868 msgid "Version matching" msgstr "" -#: ../source/specifications/version-specifiers.rst:868 +#: ../source/specifications/version-specifiers.rst:870 msgid "" "A version matching clause includes the version matching operator ``==`` and " "a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:871 +#: ../source/specifications/version-specifiers.rst:873 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:875 +#: ../source/specifications/version-specifiers.rst:877 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 " @@ -19815,7 +19860,7 @@ msgid "" "length." msgstr "" -#: ../source/specifications/version-specifiers.rst:881 +#: ../source/specifications/version-specifiers.rst:883 msgid "" "Whether or not strict version matching is appropriate depends on the " "specific use case for the version specifier. Automated tools SHOULD at least " @@ -19823,7 +19868,7 @@ msgid "" "used inappropriately." msgstr "" -#: ../source/specifications/version-specifiers.rst:886 +#: ../source/specifications/version-specifiers.rst:888 msgid "" "Prefix matching may be requested instead of strict comparison, by appending " "a trailing ``.*`` to the version identifier in the version matching clause. " @@ -19833,21 +19878,21 @@ msgid "" "(or the lack thereof) in the release segment are also ignored." msgstr "" -#: ../source/specifications/version-specifiers.rst:893 -#: ../source/specifications/version-specifiers.rst:954 +#: ../source/specifications/version-specifiers.rst:895 +#: ../source/specifications/version-specifiers.rst:956 msgid "" "For example, given the version ``1.1.post1``, the following clauses would " "match or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:900 +#: ../source/specifications/version-specifiers.rst:902 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:908 +#: ../source/specifications/version-specifiers.rst:910 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 " @@ -19855,7 +19900,7 @@ msgid "" "or not as shown::" msgstr "" -#: ../source/specifications/version-specifiers.rst:920 +#: ../source/specifications/version-specifiers.rst:922 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 " @@ -19864,7 +19909,7 @@ msgid "" "either in a prefix match wouldn't make any sense." msgstr "" -#: ../source/specifications/version-specifiers.rst:926 +#: ../source/specifications/version-specifiers.rst:928 msgid "" "The use of ``==`` (without at least the wildcard suffix) when defining " "dependencies for published distributions is strongly discouraged as it " @@ -19874,14 +19919,14 @@ msgid "" "distribution index." msgstr "" -#: ../source/specifications/version-specifiers.rst:933 +#: ../source/specifications/version-specifiers.rst:935 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:937 +#: ../source/specifications/version-specifiers.rst:939 msgid "" "If the specified version identifier is a local version identifier, then the " "local version labels of candidate versions MUST be considered when matching " @@ -19890,29 +19935,29 @@ msgid "" "strict string equality comparison." msgstr "" -#: ../source/specifications/version-specifiers.rst:945 +#: ../source/specifications/version-specifiers.rst:947 #, fuzzy msgid "Version exclusion" msgstr "翻譯" -#: ../source/specifications/version-specifiers.rst:947 +#: ../source/specifications/version-specifiers.rst:949 msgid "" "A version exclusion clause includes the version exclusion operator ``!=`` " "and a version identifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:950 +#: ../source/specifications/version-specifiers.rst:952 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:963 +#: ../source/specifications/version-specifiers.rst:965 msgid "Inclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:965 +#: ../source/specifications/version-specifiers.rst:967 msgid "" "An inclusive ordered comparison clause includes a comparison operator and a " "version identifier, and will match any version where the comparison is " @@ -19921,27 +19966,27 @@ msgid "" "`Version scheme`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:971 +#: ../source/specifications/version-specifiers.rst:973 msgid "The inclusive ordered comparison operators are ``<=`` and ``>=``." msgstr "" -#: ../source/specifications/version-specifiers.rst:973 -#: ../source/specifications/version-specifiers.rst:1003 +#: ../source/specifications/version-specifiers.rst:975 +#: ../source/specifications/version-specifiers.rst:1005 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:976 -#: ../source/specifications/version-specifiers.rst:1006 +#: ../source/specifications/version-specifiers.rst:978 +#: ../source/specifications/version-specifiers.rst:1008 msgid "Local version identifiers are NOT permitted in this version specifier." msgstr "" -#: ../source/specifications/version-specifiers.rst:980 +#: ../source/specifications/version-specifiers.rst:982 msgid "Exclusive ordered comparison" msgstr "" -#: ../source/specifications/version-specifiers.rst:982 +#: ../source/specifications/version-specifiers.rst:984 msgid "" "The exclusive ordered comparisons ``>`` and ``<`` are similar to the " "inclusive ordered comparisons in that they rely on the relative position of " @@ -19951,7 +19996,7 @@ msgid "" "specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:988 +#: ../source/specifications/version-specifiers.rst:990 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 " @@ -19961,13 +20006,13 @@ msgid "" "and ``1.7.0.post3`` but not ``1.7.0``." msgstr "" -#: ../source/specifications/version-specifiers.rst:995 +#: ../source/specifications/version-specifiers.rst:997 msgid "" "The exclusive ordered comparison ``>V`` **MUST NOT** match a local version " "of the specified version." msgstr "" -#: ../source/specifications/version-specifiers.rst:998 +#: ../source/specifications/version-specifiers.rst:1000 msgid "" "The exclusive ordered comparison ``=`` entry as part " "of the URL fragment." msgstr "" -#: ../source/specifications/version-specifiers.rst:1127 +#: ../source/specifications/version-specifiers.rst:1129 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 " @@ -20187,7 +20232,7 @@ msgid "" "systems that do not provide hash based commit identifiers." msgstr "" -#: ../source/specifications/version-specifiers.rst:1133 +#: ../source/specifications/version-specifiers.rst:1135 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 " @@ -20195,7 +20240,7 @@ msgid "" "notation." msgstr "" -#: ../source/specifications/version-specifiers.rst:1140 +#: ../source/specifications/version-specifiers.rst:1142 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 " @@ -20206,15 +20251,15 @@ msgid "" "*hash*, less so)." msgstr "" -#: ../source/specifications/version-specifiers.rst:1148 +#: ../source/specifications/version-specifiers.rst:1150 msgid "Remote URL examples::" msgstr "" -#: ../source/specifications/version-specifiers.rst:1156 +#: ../source/specifications/version-specifiers.rst:1158 msgid "File URLs" msgstr "" -#: ../source/specifications/version-specifiers.rst:1158 +#: ../source/specifications/version-specifiers.rst:1160 msgid "" "File URLs take the form of ``file:///``. If the ```` is " "omitted it is assumed to be ``localhost`` and even if the ```` is " @@ -20222,7 +20267,7 @@ msgid "" "file path on the filesystem that is to be accessed." msgstr "" -#: ../source/specifications/version-specifiers.rst:1163 +#: ../source/specifications/version-specifiers.rst:1165 msgid "" "On the various \\*nix operating systems the only allowed values for " "```` is for it to be omitted, ``localhost``, or another FQDN that the " @@ -20230,7 +20275,7 @@ msgid "" "``file://`` scheme can only be used to access paths on the local machine." msgstr "" -#: ../source/specifications/version-specifiers.rst:1168 +#: ../source/specifications/version-specifiers.rst:1170 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 " @@ -20242,43 +20287,43 @@ msgid "" "b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`_." msgstr "" -#: ../source/specifications/version-specifiers.rst:1179 +#: ../source/specifications/version-specifiers.rst:1181 msgid "Summary of differences from pkg_resources.parse_version" msgstr "" -#: ../source/specifications/version-specifiers.rst:1181 +#: ../source/specifications/version-specifiers.rst:1183 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:1185 +#: ../source/specifications/version-specifiers.rst:1187 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:1189 +#: ../source/specifications/version-specifiers.rst:1191 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:1193 +#: ../source/specifications/version-specifiers.rst:1195 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:1202 +#: ../source/specifications/version-specifiers.rst:1204 msgid "Appendix: Parsing version strings with regular expressions" msgstr "" -#: ../source/specifications/version-specifiers.rst:1204 +#: ../source/specifications/version-specifiers.rst:1206 msgid "" "As noted earlier in the :ref:`public-version-identifiers` section, published " "version identifiers SHOULD use the canonical format. This section provides " @@ -20287,20 +20332,20 @@ msgid "" "normalization." msgstr "" -#: ../source/specifications/version-specifiers.rst:1210 +#: ../source/specifications/version-specifiers.rst:1212 msgid "" "To test whether a version identifier is in the canonical format, you can use " "the following function:" msgstr "" -#: ../source/specifications/version-specifiers.rst:1219 +#: ../source/specifications/version-specifiers.rst:1221 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:1266 +#: ../source/specifications/version-specifiers.rst:1268 msgid "August 2014: This specification was approved through :pep:`440`." msgstr "" @@ -20378,6 +20423,310 @@ msgstr "" msgid "May 2012: This specification was approved through :pep:`405`." msgstr "" +#: ../source/specifications/well-known-project-urls.rst:5 +#, fuzzy +#| msgid "Project name" +msgid "Well-known Project URLs in Metadata" +msgstr "專案名稱" + +#: ../source/specifications/well-known-project-urls.rst:9 +msgid "" +"This document is primarily of interest to metadata *consumers*, who should " +"use the normalization rules and well-known list below to make their " +"presentation of project URLs consistent across the Python ecosystem." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:14 +msgid "" +"Metadata *producers* (such as build tools and individual package " +"maintainers) may continue to use any labels they please, within the overall " +"``Project-URL`` length restrictions. However, when possible, users are " +"*encouraged* to pick meaningful labels that normalize to well-known labels." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:22 +msgid "" +"See :ref:`Writing your pyproject.toml - urls ` " +"for user-oriented guidance on choosing project URL labels in your package's " +"metadata." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:26 +msgid "This specification was originally defined in :pep:`753`." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:28 +msgid "" +":pep:`753` deprecates the :ref:`core-metadata-home-page` and :ref:`core-" +"metadata-download-url` metadata fields in favor of :ref:`core-metadata-" +"project-url`, and defines a normalization and lookup procedure for " +"determining whether a ``Project-URL`` is \"well-known,\" i.e. has the " +"semantics assigned to ``Home-page``, ``Download-URL``, or other common " +"project URLs." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:35 +msgid "" +"This allows indices (such as the Python Package Index) and other downstream " +"metadata consumers to present project URLs in a consistent manner." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:42 +#, fuzzy +msgid "Label normalization" +msgstr "翻譯" + +#: ../source/specifications/well-known-project-urls.rst:46 +msgid "" +"Label normalization is performed by metadata *consumers*, not metadata " +"producers." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:49 +msgid "" +"To determine whether a ``Project-URL`` label is \"well-known,\" metadata " +"consumers should normalize the label before comparing it to the :ref:`list " +"of well-known labels `." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:53 +msgid "" +"The normalization procedure for ``Project-URL`` labels is defined by the " +"following Python function:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:65 +msgid "" +"In plain language: a label is *normalized* by deleting all ASCII punctuation " +"and whitespace, and then converting the result to lowercase." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:68 +msgid "" +"The following table shows examples of labels before (raw) and after " +"normalization:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:74 +msgid "Raw" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:75 +#, fuzzy +msgid "Normalized" +msgstr "翻譯" + +#: ../source/specifications/well-known-project-urls.rst:76 +msgid "``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:77 +#: ../source/specifications/well-known-project-urls.rst:79 +#: ../source/specifications/well-known-project-urls.rst:81 +msgid "``homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:78 +msgid "``Home-page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:80 +msgid "``Home page``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:82 +msgid "``Change_Log``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:83 +msgid "``changelog``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:84 +msgid "``What's New?``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:85 +msgid "``whatsnew``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:86 +#: ../source/specifications/well-known-project-urls.rst:87 +msgid "``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:92 +msgid "Well-known labels" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:96 +msgid "" +"The list of well-known labels is a living standard, maintained as part of " +"this document." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:99 +msgid "" +"The following table lists labels that are well-known for the purpose of " +"specializing the presentation of ``Project-URL`` metadata:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:105 +msgid "Label (Human-readable equivalent)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:107 +msgid "Aliases" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:108 +msgid "``homepage`` (Homepage)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:109 +msgid "The project's home page" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:110 +#: ../source/specifications/well-known-project-urls.rst:116 +#: ../source/specifications/well-known-project-urls.rst:122 +msgid "*(none)*" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:111 +msgid "``source`` (Source Code)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:112 +msgid "The project's hosted source code or repository" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:113 +msgid "``repository``, ``sourcecode``, ``github``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:114 +msgid "``download`` (Download)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:115 +msgid "" +"A download URL for the current distribution, equivalent to ``Download-URL``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:117 +msgid "``changelog`` (Changelog)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:118 +msgid "The project's comprehensive changelog" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:119 +msgid "``changes``, ``whatsnew``, ``history``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:120 +msgid "``releasenotes`` (Release Notes)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:121 +msgid "The project's curated release notes" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:123 +msgid "``documentation`` (Documentation)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:124 +msgid "The project's online documentation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:125 +msgid "``docs``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:126 +msgid "``issues`` (Issue Tracker)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:127 +msgid "The project's bug tracker" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:128 +msgid "``bugs``, ``issue``, ``tracker``, ``issuetracker``, ``bugtracker``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:129 +msgid "``funding`` (Funding)" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:130 +msgid "Funding Information" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:131 +msgid "``sponsor``, ``donate``, ``donation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:133 +msgid "" +"Package metadata consumers may choose to render aliased labels the same as " +"their \"parent\" well known label, or further specialize them." +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:137 +msgid "Example behavior" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:139 +msgid "" +"The following shows the flow of project URL metadata from ``pyproject.toml`` " +"to core metadata to a potential index presentation:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:142 +msgid "Example project URLs in standard configuration" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:151 +msgid "Core metadata representation" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:159 +msgid "Potential rendering" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:167 +msgid "" +"Observe that the core metadata appears in the form provided by the user " +"(since metadata *producers* do not perform normalization), but the metadata " +"*consumer* normalizes and identifies appropriate human-readable equivalents " +"based on the normalized form:" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:172 +msgid "``Home page`` becomes ``homepage``, which is rendered as ``Homepage``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:173 +msgid "" +"``DOCUMENTATION`` becomes ``documentation``, which is rendered as " +"``Documentation``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:174 +msgid "" +"``Repository`` becomes ``repository``, which is rendered as ``Source Code``" +msgstr "" + +#: ../source/specifications/well-known-project-urls.rst:175 +msgid "" +"``GitHub`` becomes ``github``, which is rendered as ``Source Code (GitHub)`` " +"(as a specialization of ``Source Code``)" +msgstr "" + #: ../source/support.rst:3 msgid "How to Get Support" msgstr "" From e9d4e73f9cb37a803cb1c3307cbd6a265ba4eb4c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Milan=20=C5=A0alka?= Date: Sun, 3 Nov 2024 07:00:31 +0100 Subject: [PATCH 2/4] Translated using Weblate (Slovak) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Currently translated at 3.4% (124 of 3600 strings) Co-authored-by: Milan Šalka Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/sk/ Translation: pypa/packaging.python.org --- locales/sk/LC_MESSAGES/messages.po | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index 2f65c6044..10d51f389 100644 --- a/locales/sk/LC_MESSAGES/messages.po +++ b/locales/sk/LC_MESSAGES/messages.po @@ -1,23 +1,23 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2013–2020, PyPA # This file is distributed under the same license as the Python Packaging User Guide package. -# Milan Šalka , 2023. +# Milan Šalka , 2023, 2024. # Rafael Fontenelle , 2024. msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-10-30 00:39+0000\n" -"PO-Revision-Date: 2024-04-25 06:07+0000\n" -"Last-Translator: Rafael Fontenelle \n" -"Language-Team: Slovak \n" +"PO-Revision-Date: 2024-11-02 00:54+0000\n" +"Last-Translator: Milan Šalka \n" +"Language-Team: Slovak \n" "Language: sk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=((n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2);\n" -"X-Generator: Weblate 5.5.1-dev\n" +"X-Generator: Weblate 5.8.2-dev\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -3296,7 +3296,7 @@ msgstr "" #: ../source/specifications/core-metadata.rst:194 #: ../source/specifications/well-known-project-urls.rst:106 msgid "Description" -msgstr "" +msgstr "Poznámka" #: ../source/guides/analyzing-pypi-package-downloads.rst:77 #: ../source/specifications/dependency-specifiers.rst:29 @@ -11689,7 +11689,7 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:22 msgid "Details" -msgstr "" +msgstr "Detaily" #: ../source/specifications/binary-distribution-format.rst:25 msgid "Installing a wheel 'distribution-1.0-py32-none-any.whl'" From 43449e4183471c9702697bf69f2275704d34b2c1 Mon Sep 17 00:00:00 2001 From: moto kawasaki Date: Sun, 3 Nov 2024 07:00:32 +0100 Subject: [PATCH 3/4] Translated using Weblate (Japanese) Currently translated at 95.2% (3254 of 3418 strings) Co-authored-by: moto kawasaki Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ja/ Translation: pypa/packaging.python.org --- locales/ja/LC_MESSAGES/messages.po | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/locales/ja/LC_MESSAGES/messages.po b/locales/ja/LC_MESSAGES/messages.po index d2514ac97..edaf28cdc 100644 --- a/locales/ja/LC_MESSAGES/messages.po +++ b/locales/ja/LC_MESSAGES/messages.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-06-19 16:34+0000\n" -"PO-Revision-Date: 2024-10-30 00:02+0000\n" +"PO-Revision-Date: 2024-11-03 06:00+0000\n" "Last-Translator: moto kawasaki \n" "Language-Team: Japanese \n" @@ -19,7 +19,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Weblate 5.8.2-dev\n" +"X-Generator: Weblate 5.8.2\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -25516,11 +25516,14 @@ msgid "" "``0`` explicitly. This allows versions such as ``1.2.dev`` which is " "normalized to ``1.2.dev0``." msgstr "" +"開発リリースでは、数字部分を省略することができて、その場合には暗黙裡に ``0`` " +"であるものと見做されます。これの標準形式は、明示的に ``0`` " +"を含める形です。これによって、標準化すれば ``1.2.dev0`` となる ``1.2.dev`` " +"のようなバージョン番号を許容します。" #: ../source/specifications/version-specifiers.rst:510 -#, fuzzy msgid "Local version segments" -msgstr "ローカルのバージョン指定子" +msgstr "ローカルのバージョン番号構成部分" #: ../source/specifications/version-specifiers.rst:512 msgid "" From 425099fd082ec07ba8d82f8dd97d606f49213e74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=ED=99=A9=EC=9D=B8=EC=95=84?= Date: Sun, 3 Nov 2024 07:00:33 +0100 Subject: [PATCH 4/4] Translated using Weblate (Korean) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Currently translated at 2.3% (83 of 3600 strings) Co-authored-by: 황인아 Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ko/ Translation: pypa/packaging.python.org --- locales/ko/LC_MESSAGES/messages.po | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index f1f5f7f42..c02627532 100644 --- a/locales/ko/LC_MESSAGES/messages.po +++ b/locales/ko/LC_MESSAGES/messages.po @@ -7,21 +7,22 @@ # kkumtree , 2023. # Bae KwonHan , 2024. # emscb , 2024. +# 황인아 , 2024. msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-10-30 00:39+0000\n" -"PO-Revision-Date: 2024-03-21 03:01+0000\n" -"Last-Translator: emscb \n" -"Language-Team: Korean \n" +"PO-Revision-Date: 2024-11-03 06:00+0000\n" +"Last-Translator: 황인아 \n" +"Language-Team: Korean \n" "Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Weblate 5.5-dev\n" +"X-Generator: Weblate 5.8.2\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -2681,7 +2682,7 @@ msgstr "" #: ../source/glossary.rst:111 msgid "Extension Module" -msgstr "" +msgstr "확장 모듈" #: ../source/glossary.rst:114 msgid ""