From 04a410b2af7b2957123209e56a33f5032a02d875 Mon Sep 17 00:00:00 2001 From: Hosted Weblate Date: Tue, 3 Sep 2024 03:09:30 +0200 Subject: [PATCH] Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Co-authored-by: Hosted Weblate Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ Translation: pypa/packaging.python.org --- locales/ar/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/ars/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/de/LC_MESSAGES/messages.po | 168 ++++++++++++++++-- locales/eo/LC_MESSAGES/messages.po | 170 +++++++++++++++++-- locales/es/LC_MESSAGES/messages.po | 171 +++++++++++++++++-- locales/fa/LC_MESSAGES/messages.po | 168 ++++++++++++++++-- locales/fil/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/fr/LC_MESSAGES/messages.po | 170 +++++++++++++++++-- locales/frc/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/gl/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/hi/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/id/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/ko/LC_MESSAGES/messages.po | 168 ++++++++++++++++-- locales/lzh/LC_MESSAGES/messages.po | 168 ++++++++++++++++-- locales/mk/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/pl/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/pt_BR/LC_MESSAGES/messages.po | 215 +++++++++++++++++++++--- locales/ro/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/ru/LC_MESSAGES/messages.po | 215 +++++++++++++++++++++--- locales/sai/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/si/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/sk/LC_MESSAGES/messages.po | 168 ++++++++++++++++-- locales/ta/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/uk/LC_MESSAGES/messages.po | 176 +++++++++++++++++-- locales/vi/LC_MESSAGES/messages.po | 166 ++++++++++++++++-- locales/zh_Hans/LC_MESSAGES/messages.po | 177 +++++++++++++++++-- locales/zh_Hant/LC_MESSAGES/messages.po | 172 +++++++++++++++++-- 27 files changed, 4213 insertions(+), 417 deletions(-) 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/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 ""