diff --git a/locales/ar/LC_MESSAGES/messages.po b/locales/ar/LC_MESSAGES/messages.po index 437c6f06a..b56cfcf5e 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-01-18 07:31+0000\n" "Last-Translator: Youcef Guenaoua \n" "Language-Team: Arabic `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6872,6 +6987,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8451,25 +8585,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8544,7 +8680,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/ars/LC_MESSAGES/messages.po b/locales/ars/LC_MESSAGES/messages.po index 4093cf978..53c414c18 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/de/LC_MESSAGES/messages.po b/locales/de/LC_MESSAGES/messages.po index c6f08cc00..6b94005d2 100644 --- a/locales/de/LC_MESSAGES/messages.po +++ b/locales/de/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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-04-22 14:28+0000\n" "Last-Translator: Pixel-Master \n" "Language-Team: German `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6927,6 +7044,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8509,25 +8645,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8602,7 +8740,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/eo/LC_MESSAGES/messages.po b/locales/eo/LC_MESSAGES/messages.po index 0e323af45..07dbac72d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2021-08-06 05:45+0000\n" "Last-Translator: meowmeowmeowcat \n" "Language-Team: Esperanto `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`Poetry `_" +msgid "`Hatchling `_" +msgstr "`Poetry `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -7058,6 +7177,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8659,25 +8797,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8752,7 +8892,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/es/LC_MESSAGES/messages.po b/locales/es/LC_MESSAGES/messages.po index c27ae4051..7d20c88ad 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-29 09:35+0000\n" "Last-Translator: gallegonovato \n" "Language-Team: Spanish `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +msgid "`Hatchling `_" +msgstr "`Poetry `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -7142,6 +7262,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8733,25 +8872,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8826,7 +8967,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/fa/LC_MESSAGES/messages.po b/locales/fa/LC_MESSAGES/messages.po index cdffd6a50..14f8e9b17 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2023-02-15 07:52+0000\n" "Last-Translator: Arsalan Dehghani \n" "Language-Team: Persian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6885,6 +7002,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8470,25 +8606,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8563,7 +8701,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/fil/LC_MESSAGES/messages.po b/locales/fil/LC_MESSAGES/messages.po index 14c25b155..f9df9f9c4 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2022-11-19 08:28+0000\n" "Last-Translator: RedFurrFox \n" "Language-Team: Filipino `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6873,6 +6988,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8452,25 +8586,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8545,7 +8681,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/fr/LC_MESSAGES/messages.po b/locales/fr/LC_MESSAGES/messages.po index 4a027f9d6..acfa194fd 100644 --- a/locales/fr/LC_MESSAGES/messages.po +++ b/locales/fr/LC_MESSAGES/messages.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-04-25 06:07+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: French `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -7133,6 +7252,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8724,25 +8862,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8817,7 +8957,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/frc/LC_MESSAGES/messages.po b/locales/frc/LC_MESSAGES/messages.po index ab34b8345..cc5a3494d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/gl/LC_MESSAGES/messages.po b/locales/gl/LC_MESSAGES/messages.po index 16666281c..bbfe3699d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/hi/LC_MESSAGES/messages.po b/locales/hi/LC_MESSAGES/messages.po index 98ad98e44..c2d650e28 100644 --- a/locales/hi/LC_MESSAGES/messages.po +++ b/locales/hi/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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2022-09-29 05:18+0000\n" "Last-Translator: Aryan 'Ba3a' Kumar \n" "Language-Team: Hindi `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6913,6 +7028,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8494,25 +8628,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8587,7 +8723,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/id/LC_MESSAGES/messages.po b/locales/id/LC_MESSAGES/messages.po index f91c67a66..40f2dbe97 100644 --- a/locales/id/LC_MESSAGES/messages.po +++ b/locales/id/LC_MESSAGES/messages.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-01-27 05:01+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Indonesian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6918,6 +7033,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8503,25 +8637,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8596,7 +8732,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/ja/LC_MESSAGES/messages.po b/locales/ja/LC_MESSAGES/messages.po index 58870ede6..aff34fecd 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-08-16 07:22+0000\n" +"PO-Revision-Date: 2024-09-05 02:09+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.7\n" +"X-Generator: Weblate 5.7.2-rc\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -23280,6 +23280,12 @@ msgid "" "been \"Yanked\" as per :ref:`the API yank specification `." msgstr "" +"``yanked``: **オプション** のキーで、当該ファイルがヤンクされたものか否かを示" +"すブーリアンか、または、ファイルがヤンクされるに至った特定の理由を示す任意の" +"空ではない文字列か、いずれかの値を持ちます。 ``yanked`` " +"キーが存在して値が真であれば、``url`` " +"フィールドによって指し示されるファイルが :ref:`API ヤンク仕様 ` にある通りに \"ヤンク\" されたことを示します。" #: ../source/specifications/simple-repository-api.rst:529 msgid "" @@ -23290,11 +23296,15 @@ msgid "" "best thought of as a set, but both JSON and HTML lack the functionality to " "have sets." msgstr "" +"``files`` キーは配列なのである種の順序があることが要求される一方で、 :ref:`" +"基本となる HTML API の仕様 ` にもこの仕様にも、特" +"定の順序付けも要求されていませんし、あるリクエストと次のそれの間で順序が保た" +"れるということも要求されていません。心情としては、これは集合であると考えるの" +"が最適ですが、JSON にも HTML にも集合を扱う機能は欠落しています。" #: ../source/specifications/simple-repository-api.rst:538 -#, fuzzy msgid "Content-Types" -msgstr "内容" +msgstr "Content-Types" #: ../source/specifications/simple-repository-api.rst:540 msgid "" @@ -23303,10 +23313,14 @@ msgid "" "response), what version of the API it represents, and what serialization " "format has been used." msgstr "" +"この仕様では、シンプル API からの応答はすべて、その応答が何であるか (" +"シンプル API からの応答である) 、どのバージョンの API を表現しているか、また" +"、使われているシリアル化フォーマットは何であるかを記述する標準のコンテント型" +"を持ちます。" #: ../source/specifications/simple-repository-api.rst:544 msgid "The structure of this content type will be:" -msgstr "" +msgstr "このコンテント型の構造はこのようになっていることでしょう:" #: ../source/specifications/simple-repository-api.rst:550 msgid "" @@ -23315,18 +23329,24 @@ msgid "" "included in the content type, and will be prefixed with a ``v`` to clarify " "that it is a version number." msgstr "" +"これらの API からの応答のうちのひとつをクライアントが理解しようと試みる際には" +"、メジャーバージョンだけが継続不可能にするものであるべきなので、メジャーバー" +"ジョンだけがコンテント型に含まれるでしょうし、" +"それがバージョン番号であることを明確にするために前に ``v`` " +"をつけられることになるでしょう。" #: ../source/specifications/simple-repository-api.rst:555 msgid "Which means that for the existing 1.0 API, the content types would be:" -msgstr "" +msgstr "ということは、既存の 1.0 API " +"においては、コンテント型はこのようになるでしょう:" #: ../source/specifications/simple-repository-api.rst:557 msgid "**JSON:** ``application/vnd.pypi.simple.v1+json``" -msgstr "" +msgstr "**JSON:** ``application/vnd.pypi.simple.v1+json``" #: ../source/specifications/simple-repository-api.rst:558 msgid "**HTML:** ``application/vnd.pypi.simple.v1+html``" -msgstr "" +msgstr "**HTML:** ``application/vnd.pypi.simple.v1+html``" #: ../source/specifications/simple-repository-api.rst:560 msgid "" @@ -23336,6 +23356,11 @@ msgid "" "recommended however, that clients be explicit about what versions they " "support." msgstr "" +"上記に加えて、特別な \"meta\" バージョンが ``latest`` という名前でサポートさ" +"れており、その目的はクライアントが完全に最新のバージョンをリクエストすること" +"を許すためであり、そのバージョンが何であるかを前もって知ることを不要にするた" +"めです。しかしながら、クライアントは自身がどのバージョンをサポートしているの" +"かを明示的に示すことが推奨されています。" #: ../source/specifications/simple-repository-api.rst:565 msgid "" @@ -23344,11 +23369,14 @@ msgid "" "``text/html`` content type, this spec further defines ``text/html`` as an " "alias for the ``application/vnd.pypi.simple.v1+html`` content type." msgstr "" +"既存の :ref:`基本となる HTML API の仕様 ` の API " +"応答が ``text/html`` コンテント型を使うことを期待している既存のクライアント群" +"をサポートするために、この仕様では、さらに、 ``text/html`` を ``application/" +"vnd.pypi.simple.v1+html`` コンテント型へのエイリアスであると定義しています。" #: ../source/specifications/simple-repository-api.rst:572 -#, fuzzy msgid "Version + Format Selection" -msgstr "バージョン指定子" +msgstr "バージョン + フォーマットの選択" #: ../source/specifications/simple-repository-api.rst:574 msgid "" @@ -23358,6 +23386,12 @@ msgid "" "version to the API can be added without disrupting existing clients " "expecting the previous API version." msgstr "" +"今や複数の可能なシリアル化が存在するので、クライアント群がどのシリアル化フォ" +"ーマットであれば理解できるのかを示すことができるようにする必要があります。加" +"えて、以前の API " +"バージョンを期待している既存のクライアント群の妨げとなることなしに、どんな " +"API の可能な新しいメジャーバージョンでも追加することができれば利益があること" +"でしょう。" #: ../source/specifications/simple-repository-api.rst:579 msgid "" @@ -23365,18 +23399,23 @@ msgid "" "Content Negotiation `_." msgstr "" +"これを可能にするために、この仕様では、 HTTP の `" +"サーバ主導のコンテントネゴシエーション `_ の使用を標準化します。" #: ../source/specifications/simple-repository-api.rst:582 msgid "" "While this spec won't fully describe the entirety of server-driven content " "negotiation, the flow is roughly:" -msgstr "" +msgstr "この仕様では、サーバ主導のコンテントネゴシエーションについて完全にすべてを記" +"述することはありませんが、流れは大まかに次のようになります:" #: ../source/specifications/simple-repository-api.rst:585 msgid "" "The client makes an HTTP request containing an ``Accept`` header listing all " "of the version+format content types that they are able to understand." -msgstr "" +msgstr "理解できるコンテント型を全て``Accept`` ヘッダに列挙した HTTP " +"リクエストをクライアントが作成します。" #: ../source/specifications/simple-repository-api.rst:587 msgid "" @@ -23384,6 +23423,9 @@ msgid "" "then returns a response using that content type (treating the absence of an " "``Accept`` header as ``Accept: */*``)." msgstr "" +"サーバはそのヘッダを検証して、列挙されたコンテント型からひとつを選択して、" +"そのコンテント型を使って応答を返します (``Accept`` " +"ヘッダが欠落している場合は ``Accept: */*`` であるものとして扱います) 。" #: ../source/specifications/simple-repository-api.rst:590 msgid "" @@ -23391,12 +23433,16 @@ msgid "" "header then they are able to choose between 3 different options for how to " "respond:" msgstr "" +"``Accept`` ヘッダにあるコンテント型のいずれもサーバがサポートしていない場合に" +"は、どのように応答するかについてサーバは３個の異なるオプションから選択するこ" +"とができます:" #: ../source/specifications/simple-repository-api.rst:594 msgid "" "Select a default content type other than what the client has requested and " "return a response with that." -msgstr "" +msgstr "クライアントが要求したものではないデフォルトのコンテント型を選択して、それを" +"使って応答を返すこと。" #: ../source/specifications/simple-repository-api.rst:596 msgid "" @@ -23404,18 +23450,24 @@ msgid "" "requested content types were available, and the server was unable or " "unwilling to select a default content type to respond with." msgstr "" +"HTTP の ``406 Not Acceptable`` 応答を返すことで、要求されたコンテント型の中に" +"利用可能なものがないことを示し、サーバとしてはデフォルトのコンテント型を選択" +"して応答することができないかしたくないことを示すこと。" #: ../source/specifications/simple-repository-api.rst:599 msgid "" "Return a HTTP ``300 Multiple Choices`` response that contains a list of all " "of the possible responses that could have been chosen." msgstr "" +"HTTP の ``300 Multiple Choices`` 応答を返して、選択できるかもしれないすべての" +"可能な応答のリストを含めておくこと。" #: ../source/specifications/simple-repository-api.rst:601 msgid "" "The client interprets the response, handling the different types of " "responses that the server may have responded with." -msgstr "" +msgstr "サーバが返すかもしれない異なる応答のタイプを取り扱ってクライアントは応答を解" +"釈します。" #: ../source/specifications/simple-repository-api.rst:604 msgid "" @@ -23424,6 +23476,10 @@ msgid "" "be prepared to handle all of the possible responses in whatever way makes " "the most sense for that client." msgstr "" +"この仕様は、あるコンテント型を取り扱うことについてサーバが行った選択のどれが " +"(クライアントへ応答を) 返すことができないものであるかを指定しませんし、クライ" +"アント側がそのクライアントにとって最も意味を為す方法であればどんなものでも可" +"能な応答の全てを取り扱う準備を **しておくべきだ** とは指定しません。" #: ../source/specifications/simple-repository-api.rst:609 msgid "" @@ -23435,6 +23491,13 @@ msgid "" "response would likely just be treated the same as a ``406 Not Acceptable`` " "error." msgstr "" +"しかしながら、 ``300 Multiple Choices`` 応答がどのように解釈され得るかについ" +"て標準的なフォーマットは存在しないので、クライアント側が理解して要求するべき" +"別のコンテント型を選択する手段がないので、この仕様ではサーバがこのオプション" +"を採用することを強い非推奨にしています。加えて、" +"クライアントが別のコンテント型を **理解できるであろう** " +"とは思われず、したがって、この応答は ``406 Not Acceptable`` " +"エラーと同じ扱いを受けるのが精々であろうと思われます。" #: ../source/specifications/simple-repository-api.rst:616 msgid "" @@ -23451,18 +23514,21 @@ msgid "" "client understands and is able to process. It supports three different " "formats for each content type that is being requested:" msgstr "" +"``Accept`` ヘッダは、クライアントが理解し処理することが可能なコンテント型をカ" +"ンマで区切られたリストに列挙したものです。まさに要求されているところのコンテ" +"ント型のそれぞれについて３個の異なるフォーマットをサポートしています:" #: ../source/specifications/simple-repository-api.rst:627 msgid "``$type/$subtype``" -msgstr "" +msgstr "``$type/$subtype``" #: ../source/specifications/simple-repository-api.rst:628 msgid "``$type/*``" -msgstr "" +msgstr "``$type/*``" #: ../source/specifications/simple-repository-api.rst:629 msgid "``*/*``" -msgstr "" +msgstr "``*/*``" #: ../source/specifications/simple-repository-api.rst:631 msgid "" @@ -23470,6 +23536,9 @@ msgid "" "``$type/$subtype``, as that is the only way to actually specify the version " "and format you want." msgstr "" +"バージョン＋フォーマット の選択に使うには、" +"これらのうちで最も役に立つのは ``$type/$subtype`` " +"で、望みのバージョンとフォーマットを実際に指定する唯一の方法だからです。" #: ../source/specifications/simple-repository-api.rst:635 msgid "" @@ -23480,6 +23549,12 @@ msgid "" "header's `quality value `_ syntax." msgstr "" +"``Accept`` ヘッダに列挙されたコンテント型の順序は、なんら特定の意味を持たず、" +"サーバ側ではその全てをそれを使って応答するために等しく正当なものと " +"**考えるべきです** 。クライアント側が特定のコンテント型を他のものよりも好むこ" +"とを指定したいならば、 ``Accept`` ヘッダの `quality バリュー " +"`_ " +"の文法を使っても構いません。" #: ../source/specifications/simple-repository-api.rst:642 msgid "" @@ -23490,6 +23565,11 @@ msgid "" "lower quality, and any entry without a quality present will default to a " "quality of ``1``." msgstr "" +"これは、 ``;q=`` とこれに後続する10進数で3桁までの ``0`` 以上 ``1`` " +"以下の値を付加することによって ``Accept`` ヘッダ内の特定のエントリの優先度を" +"クライアントが指定することを可能にします。この値を解釈する際には、より高い q " +"値 (quality 値) のエントリがより低い品質のものよりも優先され、q " +"値を持たないものはデフォルトで ``1`` であると解釈されます。" #: ../source/specifications/simple-repository-api.rst:648 msgid "" @@ -23498,6 +23578,10 @@ msgid "" "priority, and it may even return a content type that they did **not** ask " "for." msgstr "" +"しかしながら、サーバはクライアント側から要請されたコンテント型の **どれ** " +"を選んでも構わないということ、そして、サーバはクライアントが " +"**要請しなかった** コンテント型で返答しても構わないということを、クライアント" +"は心に留めておくべきです。" #: ../source/specifications/simple-repository-api.rst:652 msgid "" @@ -23509,10 +23593,17 @@ msgid "" "pip/blob/cf3696a81b341925f82f20cb527e656176987565/src/pip/_internal/index/" "collector.py#L123-L150>`_ so the risks for actual breakages is low." msgstr "" +"API へのリクエストから受けとった応答のコンテント型を決定するにあたってクライ" +"アントを補助するために、この仕様では、応答のコンテント型を示す ``Content-" +"Type`` ヘッダをサーバが常に含めることを要求している。これは、技術的には後方互" +"換性のない変更ですが、実際には `pip ` はすでにこの要求事項 `_ " +"を強制していますので、実際に何かを壊すリスクは低いでしょう。" #: ../source/specifications/simple-repository-api.rst:659 msgid "An example of how a client can operate would look like:" -msgstr "" +msgstr "クライアントがどのように運用できるかの例は次のように見えるでしょう:" #: ../source/specifications/simple-repository-api.rst:710 msgid "" @@ -23520,10 +23611,14 @@ msgid "" "would just remove the content types that they do not want from the " "``Accept`` header, and turn receiving them into an error." msgstr "" +"クライアント側が、 HTML だけを、または JSON だけをサポートしたいと望むなら、 " +"``Accept`` " +"ヘッダから望まないコンテント型を単に取り除くでしょうし、(望まないものを) " +"受け取ったらエラーにすることでしょう。" #: ../source/specifications/simple-repository-api.rst:716 msgid "Alternative Negotiation Mechanisms" -msgstr "" +msgstr "代わりの交渉機構 " #: ../source/specifications/simple-repository-api.rst:718 msgid "" @@ -23533,10 +23628,16 @@ msgid "" "mechanism may not be sufficient. For those cases this spec has alternative " "negotiation mechanisms that may *optionally* be used instead." msgstr "" +"HTTP でのコンテンツネゴシエーションを使うことがクライアントとサーバが協調して" +"クライアントが理解することができる HTTP 応答を得られることを確実にする標準的" +"な方法である一方で、このメカニズムで十分とは言えないような状況が存在します。" +"そのような場合向けに、この仕様には、 *オプションとして* " +"代わりに使っても構わない代わりの交渉機構 があります。" #: ../source/specifications/simple-repository-api.rst:726 msgid "URL Parameter" -msgstr "" +msgstr "URL パラメータ" #: ../source/specifications/simple-repository-api.rst:728 msgid "" @@ -23551,6 +23652,9 @@ msgid "" "types. Passing multiple content types, wild cards, quality values, etc... is " "**not** supported." msgstr "" +"``format`` パラメータの値は、正当なコンテント型のうちの **ひとつ** " +"であるべきです。複数のコンテント型を渡すことやワイルドカード、quality " +"値などはサポートされて **いません** 。" #: ../source/specifications/simple-repository-api.rst:735 msgid "" @@ -23559,12 +23663,19 @@ msgid "" "allow for easier human based exploration of the API within a browser, or to " "allow documentation or notes to link to a specific version+format." msgstr "" +"このパラメータをサポートすることはオプションで、 API " +"とやりとりするクライアントはこれを **当てにするべきではありません** " +"。このネゴシエーションメカニズムは、人間がブラウザ内で API " +"をより簡単に調査することができるようにすることを意図したもの、ないし、" +"説明文書やノートから特定の version+format " +"にリンクすることができるようにすることを意図したものです。" #: ../source/specifications/simple-repository-api.rst:740 msgid "" "Servers that do not support this parameter may choose to return an error " "when it is present, or they may simple ignore its presence." -msgstr "" +msgstr "このパラメータをサポートしないサーバの側では、これの存在時にはエラーを返すこ" +"とを選択しても構いませんし、単にその存在を無視しても構いません。" #: ../source/specifications/simple-repository-api.rst:743 msgid "" @@ -23575,11 +23686,17 @@ msgid "" "server-driven content negotiation typically has (e.g. ``406 Not Available``, " "``303 Multiple Choices``, or selecting a default type to return)." msgstr "" +"サーバがこのパラメータを実装していない時は、クライアントの ``Accept`` " +"ヘッダ内の値に何があってもそれに **高い優先度を与えるべき** で、" +"要求されたフォーマットをサーバがサポートしていないなら ``Accept`` " +"ヘッダにフォールバックすることを選択しても良いし、標準的なサーバ側が駆動する" +"コンテントネゴシエーションが典型的に持っているエラーコンディション (例えば、 " +"``406 Not Available`` や ``303 Multiple Choices`` " +"、ないし、応答のデフォルトの型) のどれでもひとつを選択しても構いません。" #: ../source/specifications/simple-repository-api.rst:752 -#, fuzzy msgid "Endpoint Configuration" -msgstr "共通の設定" +msgstr "エンドポイントの設定" #: ../source/specifications/simple-repository-api.rst:754 msgid "" @@ -23587,6 +23704,9 @@ msgid "" "consequence of using content negotiation and allowing servers to select " "which of the available content types is their default." msgstr "" +"このオプションは、技術的には何ら特別なオプションではなく、コンテントネゴシエ" +"ーションを使用することに伴う自然な結果であり、利用可能なコンテント型のいずれ" +"かを自身のデフォルトとしてサーバが選択することを許すものです。" #: ../source/specifications/simple-repository-api.rst:758 msgid "" @@ -23595,6 +23715,10 @@ msgid "" "their client to select the version they want, then that is a supported " "configuration." msgstr "" +"あるサーバがサーバ主導のコンテントネゴシエーションを実装したくないか実装する" +"ことができなくて、むしろユーザに対してクライアントが望むバージョンを選択する" +"ように明示的に要求するのであれば、それはサポートされているコンフィグレーショ" +"ンのひとつです。" #: ../source/specifications/simple-repository-api.rst:762 msgid "" @@ -23605,6 +23729,14 @@ msgid "" "client makes a request using the ``Accept`` header, the server can ignore it " "and return the content type that corresponds to that endpoint." msgstr "" +"これを有効にするためには、サーバは、複数のエンドポイント (例えば、 ``/simple/" +"v1+html/`` と ``/simple/v1+json/`` のいずれかまたは両方) " +"をサポートしたいと考える version+format " +"のそれぞれにするべきです。このようなエンドポイントのもとでは、" +"コンテント型のひとつ (またはサブセット) " +"をサポートするリポジトリのコピーをホストすることができます。クライアントが " +"``Accept`` ヘッダを使ってリクエストした時に、サーバはそれを無視して当該エンド" +"ポイントに対応するコンテント型を返すことができます。" #: ../source/specifications/simple-repository-api.rst:769 msgid "" @@ -23613,10 +23745,15 @@ msgid "" "when making a request to that server, emit an ``Accept`` header that *only* " "includes the correct content type." msgstr "" +"特定のコンフィグレーションを要求したいと願うクライアントにとっては、" +"ある特定のリポジトリ URL にどんな version+format " +"が設定されたかを追跡することができますし、" +"そのサーバへのリクエストを作成する時に正しいコンテント型 **だけ** を含んだ " +"``Accept`` ヘッダを発出することができます。" #: ../source/specifications/simple-repository-api.rst:776 msgid "TUF Support - PEP 458" -msgstr "" +msgstr "TUF サポート - PEP 458" #: ../source/specifications/simple-repository-api.rst:778 msgid "" @@ -23628,6 +23765,14 @@ msgid "" "handle the fact that a target could have multiple different representations " "that all hash differently." msgstr "" +":pep:`458` は、すべての API 応答がハッシュ可能で、リポジトリのルートからの相" +"対パスによって一意に識別できることを要求しています。シンプル API " +"リポジトリでは、ターゲットのパスは、我々の API のルート (例えば、 PyPI " +"における ``/simple/``) です。標準の HTTP クライアントを使う代わりに TUF " +"クライアントを使って API " +"にアクセスする時にはこれが試練を生み出しますが、それというのは、ハッシュが相" +"異なるような複数の異なる表現形式をターゲットが持っているかもしれないという事" +"実を TUF クライアントが扱えないからです。" #: ../source/specifications/simple-repository-api.rst:785 msgid "" @@ -23636,6 +23781,11 @@ msgid "" "words, a path like ``simple/PROJECT/`` is not acceptable, because it " "technically points to a directory." msgstr "" +":pep:`458` は、どんなターゲットパスがシンプル API " +"向けであるべきかについて指定していませんが、 TUF はターベットパスが " +"\"ファイルライク \" であることを要求し、換言すれば、 ``simple/" +"PROJECT/.`` " +"のようなパスは技術的にはディレクトリを指し示しているので受け入れ不可能です。" #: ../source/specifications/simple-repository-api.rst:790 msgid "" @@ -23645,6 +23795,11 @@ msgid "" "be fetched. This same thing can hold true for other aspects of the actual " "HTTP request, such as the ``Accept`` header." msgstr "" +"欠点を補う取り柄は、シンプル API から持ってきた URL にターゲットパスが実際に " +"*合致していなければならないということはない* ことで、取得する必要のある URL " +"の実際の形への変換の方法を取得したコードが知っていることが魔法の印形になり得" +"ます。これと同じことが、 ``Accept`` ヘッダのような実際の HTTP " +"リクエスト他の側面についても当てはまります。" #: ../source/specifications/simple-repository-api.rst:796 msgid "" @@ -23653,6 +23808,10 @@ msgid "" "defers making a decision about how exactly to represent this inside of :pep:" "`458` metadata." msgstr "" +"結局、あるディレクトリをファイル名に対応させる方法を解明することはこの仕様の" +"スコープの外にあります (しかし :pep:`458` のスコープの中にはあるでしょう) " +"が、この仕様では、 :pep:`458` のメタデータの中にこれをどれほど正確に表現する" +"のかについての決断を行うことを遅延させているのです。" #: ../source/specifications/simple-repository-api.rst:800 msgid "" @@ -23663,6 +23822,14 @@ msgid "" "the v1 HTML format would be ``simple/PROJECT/vnd.pypi.simple.v1.html`` and " "the v1 JSON format would be ``simple/PROJECT/vnd.pypi.simple.v1.json``." msgstr "" +"しかしながら、 :pep:`458` を実装しようと試みる pip に対する現在の WIP " +"ブランチは、 ``simple/PROJECT/index.html`` " +"のようなターゲットパスを使っているようです。これは、何か ``simple/PROJECT/vnd" +".pypi.simple.vN.Format`` のようなものを使うことで、 API のバージョンやシリア" +"ル化フォーマットを包含するように修正できるかもしれません。それで、 v1 の " +"HTML フォーマットは ``simple/PROJECT/vnd.pypi.v1.html`` のように、 v1 の " +"JSON フォーマットは ``simple/PROJECT/vnd.pypi.simple.v1.json`` " +"のようになることでしょう。" #: ../source/specifications/simple-repository-api.rst:807 msgid "" @@ -23670,12 +23837,17 @@ msgid "" "simple.v1+html`` when interacting through TUF, it likely will make the most " "sense to normalize to the more explicit name." msgstr "" +"このケースでは、 ``text/html`` が ``application/vnd.pypi.simple.v1+html`` " +"へのエイリアスであることから、 TUF を通じて相互作用する時にはもっと明示的な名" +"称に正規化する方が最大の意味をなすことになるでしょう。" #: ../source/specifications/simple-repository-api.rst:811 msgid "" "Likewise the ``latest`` metaversion should not be included in the targets, " "only explicitly declared versions should be supported." msgstr "" +"``latest`` メタバージョンがターゲットの中に含まれているべきではないのと同様に" +"、明示的に宣言されたバージョンだけがサポートされるべきです。" #: ../source/specifications/simple-repository-api.rst:817 msgid "" @@ -23684,6 +23856,10 @@ msgid "" "this spec, but it does **not** represent any sort of requirement to match " "these decisions." msgstr "" +"この節は 規範的ではなく、この仕様を実装する上での最善のデフォルト実装の決定だ" +"と仕様の執筆者たちが信じるものを表現していますが、しかし、" +"これらの決定に合致させるための要求事項としてはいかなるものも " +"**表現していません** 。" #: ../source/specifications/simple-repository-api.rst:821 msgid "" @@ -23693,10 +23869,15 @@ msgid "" "API provide guardrails that attempt to push clients into making the best " "choices it can." msgstr "" +"これらの決断は、 API の最新のバージョンの上に移行できるような、その一方でなる" +"べく大量の互換性も維持するような要求事項を数の上でなるべく最大化するように選" +"択されています。加えて、" +"クライアント側が最善の選択を行うようにと試みるガードレールを API " +"が提供するように試みてきました。" #: ../source/specifications/simple-repository-api.rst:826 msgid "It is recommended that servers:" -msgstr "" +msgstr "サーバには次のことが推奨されます:" #: ../source/specifications/simple-repository-api.rst:828 msgid "" @@ -23704,6 +23885,9 @@ msgid "" "content negotiation, for as long as they reasonably can, or at least as long " "as they're receiving non trivial traffic that uses the HTML responses." msgstr "" +"サーバ主導のコンテントネゴシエーションを使って、合理的に可能である限り、もし" +"くは、少なくとも HTML 応答を用いる非自明のトラフィックを受け取る限り、この仕" +"様の中で記述される３個のコンテント型の全てをサポートすること。" #: ../source/specifications/simple-repository-api.rst:832 msgid "" @@ -23712,12 +23896,20 @@ msgid "" "``300 Multiple Choice`` response, and instead return a ``406 Not " "Acceptable`` response." msgstr "" +"サーバは、" +"どのように協働すれば良いかを知っているコンテント型をひとつも含まないような " +"``Accept`` ヘッダに遭遇した時、 ``300 Multiple Choice`` " +"応答を返すべきではなく、その代わりに ``406 Not Acceptable`` " +"応答を返すべきです。" #: ../source/specifications/simple-repository-api.rst:837 msgid "" "However, if choosing to use the endpoint configuration, you should prefer to " "return a ``200 OK`` response in the expected content type for that endpoint." msgstr "" +"しかしながら、このエンドポイント設定を使うことを選択したなら、 " +"できることならそのエンドポイントが期待しているコンテント型で ``200 Ok`` " +"を返したいと考えるべきです。" #: ../source/specifications/simple-repository-api.rst:840 msgid "" @@ -23727,10 +23919,15 @@ msgid "" "requests as well as any quality priority values they have expressed, and it " "should only use the ``text/html`` content type as a last resort." msgstr "" +"受け入れ可能なバージョンを選択する時、サーバは、クライアントがサポートする中" +"で、最も表現力が豊かで機能的なシリアル化フォーマットを伴っていて、" +"クライアント側が表現したクオリティ優先度 と同じくクライア" +"ントからのリクエストの特質を考慮に入れて、最も高いバージョンを選択するべきで" +"あり、 ``text/html`` コンテント型の使用は最後の逃避先とするべきです。" #: ../source/specifications/simple-repository-api.rst:846 msgid "It is recommended that clients:" -msgstr "" +msgstr "クライアント側には次のことが推奨されます:" #: ../source/specifications/simple-repository-api.rst:848 msgid "" diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index 662a9b295..32c7ab69e 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-03-21 03:01+0000\n" "Last-Translator: emscb \n" "Language-Team: Korean `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6954,6 +7071,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8539,25 +8675,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8632,7 +8770,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/lzh/LC_MESSAGES/messages.po b/locales/lzh/LC_MESSAGES/messages.po index 571cf0388..ddf2d1118 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-01-31 06:01+0000\n" "Last-Translator: maker \n" "Language-Team: Chinese (Literary) `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6871,6 +6988,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8450,25 +8586,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8543,7 +8681,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/mk/LC_MESSAGES/messages.po b/locales/mk/LC_MESSAGES/messages.po index 2eb829b85..89a634143 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2023-10-21 04:04+0000\n" "Last-Translator: \"Kristijan \\\"Fremen\\\" Velkovski\" \n" "Language-Team: Macedonian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6875,6 +6990,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8456,25 +8590,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8549,7 +8685,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/pl/LC_MESSAGES/messages.po b/locales/pl/LC_MESSAGES/messages.po index 6fde72fa7..55fd6af0d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/pt_BR/LC_MESSAGES/messages.po b/locales/pt_BR/LC_MESSAGES/messages.po index 7a9696a00..5702b8548 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-30 13:48+0000\n" "Last-Translator: Alefsander Ribeiro Nascimento \n" "Language-Team: Portuguese (Brazil) `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +#, fuzzy +#| msgid "`Flatpak `_" +msgid "`Flit `_" +msgstr "`Flatpak `_" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`Apache `_" +msgid "`Hatchling `_" +msgstr "`Apache `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +#, fuzzy +msgid "`setuptools_scm `_" +msgstr "`Flexx `_" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "layout src vs layout plano" @@ -9071,6 +9197,25 @@ msgstr "" "`Escrevendo módulos de extensão cpython usando C++ `_" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "Empacotando pacotes de espaço de nomes" @@ -11247,33 +11392,43 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." msgstr "" -"Há uma diferença significativa entre as tabelas ``[build-system]`` e " -"``[project]``. O primeiro deve estar sempre presente, independentemente de " -"qual backend de construção você usa (já que *define* a ferramenta que você " -"usa). Este último é entendido pela *maioria* dos backends de construção mas " -"alguns backends de construção usam um formato diferente." -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:29 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:32 +#, fuzzy +#| msgid "" +#| "At the time of writing this (November 2023), Poetry_ is a notable build " +#| "backend that does not use the ``[project]`` table (it uses the ``[tool." +#| "poetry]`` table instead)." +msgid "" +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" "No momento em que este artigo foi escrito (novembro de 2023), Poetry_ era um " "backend de construção notável que não usava a tabela ``[project]`` (em vez " "disso, ele usava a tabela ``[tool.poetry]``)." -#: ../source/guides/writing-pyproject-toml.rst:35 -msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +#: ../source/guides/writing-pyproject-toml.rst:37 +#, fuzzy +#| msgid "" +#| "Also, the setuptools_ build backend supports both the ``[project]`` " +#| "table, and the older format in ``setup.cfg`` or ``setup.py``. For new " +#| "projects, it is recommended to use the ``[project]`` table, and keep " +#| "``setup.py`` only if some programmatic configuration is needed (such as " +#| "building C extensions), but the ``setup.cfg`` and ``setup.py`` formats " +#| "are still valid. See :ref:`setup-py-deprecated`." +msgid "" +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -11376,8 +11531,13 @@ msgstr "" "campo que não pode ser marcado como dinâmico." #: ../source/guides/writing-pyproject-toml.rst:133 +#, fuzzy +#| msgid "" +#| "The project name must consists of ASCII letters, digits, underscores " +#| "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or " +#| "end with an underscore, hyphen or period." msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" @@ -27122,6 +27282,19 @@ msgid "" "the file is empty)." msgstr "" +#~ msgid "" +#~ "There is a significant difference between the ``[build-system]`` and " +#~ "``[project]`` tables. The former should always be present, regardless of " +#~ "which build backend you use (since it *defines* the tool you use). The " +#~ "latter is understood by *most* build backends, but some build backends " +#~ "use a different format." +#~ msgstr "" +#~ "Há uma diferença significativa entre as tabelas ``[build-system]`` e " +#~ "``[project]``. O primeiro deve estar sempre presente, independentemente " +#~ "de qual backend de construção você usa (já que *define* a ferramenta que " +#~ "você usa). Este último é entendido pela *maioria* dos backends de " +#~ "construção mas alguns backends de construção usam um formato diferente." + #~ msgid "" #~ "Additionally, the user:password section of the URL MAY be a well-known, " #~ "non security sensitive string. A typical example is ``git`` in the case " diff --git a/locales/ro/LC_MESSAGES/messages.po b/locales/ro/LC_MESSAGES/messages.po index d961ee756..6f507cce0 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2021-08-20 01:32+0000\n" "Last-Translator: GUILHERME FERNANDES NETO \n" "Language-Team: Romanian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6875,6 +6990,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8454,25 +8588,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8547,7 +8683,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/ru/LC_MESSAGES/messages.po b/locales/ru/LC_MESSAGES/messages.po index c7c473356..2b5ece8bd 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-15 14:09+0000\n" "Last-Translator: gfbdrgng \n" "Language-Team: Russian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +#, fuzzy +#| msgid "`Flatpak `_" +msgid "`Flit `_" +msgstr "`Flatpak `_" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`Apache `_" +msgid "`Hatchling `_" +msgstr "`Apache `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +#, fuzzy +msgid "`setuptools_scm `_" +msgstr "`Flexx `_" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "src-макет против плоского макета" @@ -9114,6 +9240,25 @@ msgstr "" "`Написание модулей расширения cpython с использованием C++ `_" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "Упаковка пакетов пространства имён" @@ -11340,33 +11485,43 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -"Существует существенная разница между таблицами ``[build-system]`` и " -"``[project]``. Первая должна присутствовать всегда, независимо от того, " -"какой бэкенд сборки вы используете (поскольку она *определяет* инструмент, " -"который вы используете). Вторая понимается *большинством* бэкендов сборки, " -"но некоторые бэкенды используют другой формат." -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 +#, fuzzy +#| msgid "" +#| "At the time of writing this (November 2023), Poetry_ is a notable build " +#| "backend that does not use the ``[project]`` table (it uses the ``[tool." +#| "poetry]`` table instead)." msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" "На момент написания этой статьи (ноябрь 2023 года), Poetry_ является " "заметным бэкендом сборки, который не использует таблицу ``[project]`` " "(вместо нее используется таблица ``[tool.poetry]``)." -#: ../source/guides/writing-pyproject-toml.rst:35 -msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +#: ../source/guides/writing-pyproject-toml.rst:37 +#, fuzzy +#| msgid "" +#| "Also, the setuptools_ build backend supports both the ``[project]`` " +#| "table, and the older format in ``setup.cfg`` or ``setup.py``. For new " +#| "projects, it is recommended to use the ``[project]`` table, and keep " +#| "``setup.py`` only if some programmatic configuration is needed (such as " +#| "building C extensions), but the ``setup.cfg`` and ``setup.py`` formats " +#| "are still valid. See :ref:`setup-py-deprecated`." +msgid "" +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -11468,8 +11623,13 @@ msgstr "" "динамическое." #: ../source/guides/writing-pyproject-toml.rst:133 +#, fuzzy +#| msgid "" +#| "The project name must consists of ASCII letters, digits, underscores " +#| "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or " +#| "end with an underscore, hyphen or period." msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" @@ -29040,6 +29200,19 @@ msgstr "" "Если вы только начинаете с Python упаковки, рекомендуется придерживаться " "*регулярных пакетов* и ``__init__.py`` (даже если файл пуст)." +#~ msgid "" +#~ "There is a significant difference between the ``[build-system]`` and " +#~ "``[project]`` tables. The former should always be present, regardless of " +#~ "which build backend you use (since it *defines* the tool you use). The " +#~ "latter is understood by *most* build backends, but some build backends " +#~ "use a different format." +#~ msgstr "" +#~ "Существует существенная разница между таблицами ``[build-system]`` и " +#~ "``[project]``. Первая должна присутствовать всегда, независимо от того, " +#~ "какой бэкенд сборки вы используете (поскольку она *определяет* " +#~ "инструмент, который вы используете). Вторая понимается *большинством* " +#~ "бэкендов сборки, но некоторые бэкенды используют другой формат." + #~ msgid "" #~ "This guide is specifically for users of :ref:`setuptools`, other " #~ "packaging tools such as ``flit`` may offer similar functionality but " diff --git a/locales/sai/LC_MESSAGES/messages.po b/locales/sai/LC_MESSAGES/messages.po index 973e724b3..62f53bcd2 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/si/LC_MESSAGES/messages.po b/locales/si/LC_MESSAGES/messages.po index f7b2c4be2..4b1f04f0d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2022-06-11 08:19+0000\n" "Last-Translator: Kushan Gunasekera \n" "Language-Team: Sinhala `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6871,6 +6986,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8450,25 +8584,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8543,7 +8679,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index 763a24aff..1a18c988d 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-04-25 06:07+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Slovak `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -7019,6 +7136,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8604,25 +8740,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8697,7 +8835,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/ta/LC_MESSAGES/messages.po b/locales/ta/LC_MESSAGES/messages.po index ad2a8b7bd..76e14ef79 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -479,6 +479,7 @@ msgid "Deploying Python applications" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -498,6 +499,7 @@ msgid "Incomplete" msgstr "" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1672,6 +1674,119 @@ msgstr "" msgid ":doc:`setuptools:deprecated/commands`" msgstr "" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +msgid "Complete" +msgstr "" + +#: ../source/discussions/single-source-version.rst:8 +msgid "2024-08-24" +msgstr "" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6867,6 +6982,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8446,25 +8580,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8539,7 +8675,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/uk/LC_MESSAGES/messages.po b/locales/uk/LC_MESSAGES/messages.po index ed7320b86..d93cb0524 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-03-01 20:00+0000\n" "Last-Translator: Sviatoslav Sydorenko \n" "Language-Team: Ukrainian `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +#, fuzzy +#| msgid "`Flatpak `_" +msgid "`Flit `_" +msgstr "`Flatpak `_" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`AppImage `_" +msgid "`Hatchling `_" +msgstr "`AppImage `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +#, fuzzy +#| msgid "`Flexx `_" +msgid "`setuptools_scm `_" +msgstr "`Flexx `_" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -7332,6 +7457,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8935,25 +9079,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -9028,7 +9174,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/vi/LC_MESSAGES/messages.po b/locales/vi/LC_MESSAGES/messages.po index da7632faa..b79590b89 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-25 13:10+0000\n" "Last-Translator: Lenny Tran \n" "Language-Team: Vietnamese `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +msgid "`Hatchling `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6895,6 +7010,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8474,25 +8608,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8567,7 +8703,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/zh_Hans/LC_MESSAGES/messages.po b/locales/zh_Hans/LC_MESSAGES/messages.po index 4a9f06bfe..1b2057e4e 100644 --- a/locales/zh_Hans/LC_MESSAGES/messages.po +++ b/locales/zh_Hans/LC_MESSAGES/messages.po @@ -29,7 +29,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-30 13:48+0000\n" "Last-Translator: 大王叫我来巡山 \n" @@ -575,6 +575,7 @@ msgid "Deploying Python applications" msgstr "部署 Python 应用程序" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -594,6 +595,7 @@ msgid "Incomplete" msgstr "不完全" #: ../source/discussions/deploying-python-applications.rst:0 +#: ../source/discussions/single-source-version.rst:0 #: ../source/guides/distributing-packages-using-setuptools.rst:0 #: ../source/guides/index-mirrors-and-caches.rst:0 #: ../source/guides/installing-using-linux-tools.rst:0 @@ -1877,6 +1879,125 @@ msgstr "https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html" msgid ":doc:`setuptools:deprecated/commands`" msgstr ":doc:`setuptools:deprecated/commands`" +#: ../source/discussions/single-source-version.rst:5 +msgid "Single-sourcing the Project Version" +msgstr "" + +#: ../source/discussions/single-source-version.rst:7 +#, fuzzy +#| msgid "Incomplete" +msgid "Complete" +msgstr "不完全" + +#: ../source/discussions/single-source-version.rst:8 +#, fuzzy +#| msgid "2021-8-24" +msgid "2024-08-24" +msgstr "2021-8-24" + +#: ../source/discussions/single-source-version.rst:10 +msgid "" +"One of the challenges in building packages is that the version string can be " +"required in multiple places." +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"It needs to be specified when building the package (e.g. in :file:`pyproject." +"toml`)" +msgstr "" + +#: ../source/discussions/single-source-version.rst:13 +msgid "" +"This will make it available in the installed package’s metadata, from where " +"it will be accessible at runtime using ``importlib.metadata." +"version(\"distribution_name\")``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:15 +msgid "" +"A package may set a module attribute (e.g., ``__version__``) to provide an " +"alternative means of runtime access to the version of the imported package. " +"If this is done, the value of the attribute and that used by the build " +"system to set the distribution's version should be kept in sync in :ref:`the " +"build systems's recommended way `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`Apache `_" +msgid "`Hatchling `_" +msgstr "`Apache `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "SRC 布局与平面布局" @@ -7354,6 +7475,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8947,25 +9087,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:29 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:37 +msgid "" +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -9039,8 +9181,13 @@ msgid "" msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 +#, fuzzy +#| msgid "" +#| "The project name must consists of ASCII letters, digits, underscores " +#| "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or " +#| "end with an underscore, hyphen or period." msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr "" diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po index cd241380b..074e92dff 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-08-15 14:12+0000\n" +"POT-Creation-Date: 2024-08-24 00:21+0000\n" "PO-Revision-Date: 2024-07-03 11:26+0000\n" "Last-Translator: Ricky From Hong Kong \n" "Language-Team: Chinese (Traditional) `." +msgstr "" + +#: ../source/discussions/single-source-version.rst:17 +msgid "" +"If the code is in in a version control system (VCS), e.g. Git, the version " +"may appear in a *tag* such as ``v1.2.3``." +msgstr "" + +#: ../source/discussions/single-source-version.rst:19 +msgid "" +"To ensure that version numbers do not get out of sync, it is recommended " +"that there is a single source of truth for the version number." +msgstr "" + +#: ../source/discussions/single-source-version.rst:21 +msgid "In general, the options are:" +msgstr "" + +#: ../source/discussions/single-source-version.rst:23 +msgid "" +"If the code is in a version control system (VCS), e.g. Git, then the version " +"can be extracted from the VCS." +msgstr "" + +#: ../source/discussions/single-source-version.rst:25 +msgid "" +"The version can be hard-coded into the :file:`pyproject.toml` file -- and " +"the build system can copy it into other locations it may be required." +msgstr "" + +#: ../source/discussions/single-source-version.rst:27 +msgid "" +"The version string can be hard-coded into the source code -- either in a " +"special purpose file, such as :file:`_version.txt`, or as a attribute in a " +"module, such as :file:`__init__.py`, and the build system can extract it at " +"build time." +msgstr "" + +#: ../source/discussions/single-source-version.rst:30 +msgid "Consult your build system's documentation for their recommended method." +msgstr "" + +#: ../source/discussions/single-source-version.rst:35 +msgid "Build System Version Handling" +msgstr "" + +#: ../source/discussions/single-source-version.rst:37 +msgid "" +"The following are links to some build system's documentation for handling " +"version strings." +msgstr "" + +#: ../source/discussions/single-source-version.rst:39 +msgid "`Flit `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:41 +#, fuzzy +#| msgid "`Poetry `_" +msgid "`Hatchling `_" +msgstr "`Poetry `_" + +#: ../source/discussions/single-source-version.rst:43 +msgid "" +"`PDM `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:45 +msgid "" +"`Setuptools `_" +msgstr "" + +#: ../source/discussions/single-source-version.rst:47 +msgid "`setuptools_scm `_" +msgstr "" + #: ../source/discussions/src-layout-vs-flat-layout.rst:5 msgid "src layout vs flat layout" msgstr "" @@ -6951,6 +7072,25 @@ msgid "" "cpp_extension_modules.html>`_" msgstr "" +#: ../source/guides/packaging-binary-extensions.rst:408 +msgid "Additional considerations for binary wheels" +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:410 +msgid "" +"The `pypackaging-native `_ website " +"has additional coverage of packaging Python packages with native code. It " +"aims to provide an overview of the most important packaging issues for such " +"projects, with in-depth explanations and references." +msgstr "" + +#: ../source/guides/packaging-binary-extensions.rst:415 +msgid "" +"Examples of topics covered are non-Python compiled dependencies (\"native " +"dependencies\"), the importance of the ABI (Application Binary Interface) of " +"native code, dependency on SIMD code and cross compilation." +msgstr "" + #: ../source/guides/packaging-namespace-packages.rst:5 msgid "Packaging namespace packages" msgstr "" @@ -8536,25 +8676,27 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:25 msgid "" -"There is a significant difference between the ``[build-system]`` and " -"``[project]`` tables. The former should always be present, regardless of " -"which build backend you use (since it *defines* the tool you use). The " -"latter is understood by *most* build backends, but some build backends use a " -"different format." +"The ``[build-system]`` table should always be present, regardless of which " +"build backend you use (``[build-system]`` *defines* the build tool you use)." +msgstr "" + +#: ../source/guides/writing-pyproject-toml.rst:29 +msgid "" +"On the other hand, the ``[project]`` table is understood by *most* build " +"backends, but some build backends use a different format." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:31 +#: ../source/guides/writing-pyproject-toml.rst:32 msgid "" -"At the time of writing this (November 2023), Poetry_ is a notable build " -"backend that does not use the ``[project]`` table (it uses the ``[tool." -"poetry]`` table instead)." +"As of August 2024, Poetry_ is a notable build backend that does not use the " +"``[project]`` table, it uses the ``[tool.poetry]`` table instead. Also, the " +"setuptools_ build backend supports both the ``[project]`` table, and the " +"older format in ``setup.cfg`` or ``setup.py``." msgstr "" -#: ../source/guides/writing-pyproject-toml.rst:35 +#: ../source/guides/writing-pyproject-toml.rst:37 msgid "" -"Also, the setuptools_ build backend supports both the ``[project]`` table, " -"and the older format in ``setup.cfg`` or ``setup.py``. For new projects, it " -"is recommended to use the ``[project]`` table, and keep ``setup.py`` only if " +"For new projects, use the ``[project]`` table, and keep ``setup.py`` only if " "some programmatic configuration is needed (such as building C extensions), " "but the ``setup.cfg`` and ``setup.py`` formats are still valid. See :ref:" "`setup-py-deprecated`." @@ -8629,7 +8771,7 @@ msgstr "" #: ../source/guides/writing-pyproject-toml.rst:133 msgid "" -"The project name must consists of ASCII letters, digits, underscores " +"The project name must consist of ASCII letters, digits, underscores " "\"``_``\", hyphens \"``-``\" and periods \"``.``\". It must not start or end " "with an underscore, hyphen or period." msgstr ""