From 289bd55c5650e7a4542f3b51c56aa081f72dfe54 Mon Sep 17 00:00:00 2001 From: Hosted Weblate Date: Tue, 21 Jan 2025 13:33:04 +0100 Subject: [PATCH] Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pypa/packaging.python.org Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ --- locales/ar/LC_MESSAGES/messages.po | 154 +++++++------ locales/ars/LC_MESSAGES/messages.po | 150 +++++++------ locales/de/LC_MESSAGES/messages.po | 154 +++++++------ locales/eo/LC_MESSAGES/messages.po | 282 ++++++++++++------------ locales/es/LC_MESSAGES/messages.po | 150 +++++++------ locales/fa/LC_MESSAGES/messages.po | 150 +++++++------ locales/fil/LC_MESSAGES/messages.po | 150 +++++++------ locales/fr/LC_MESSAGES/messages.po | 150 +++++++------ locales/frc/LC_MESSAGES/messages.po | 150 +++++++------ locales/gl/LC_MESSAGES/messages.po | 150 +++++++------ locales/gmh/LC_MESSAGES/messages.po | 150 +++++++------ locales/hi/LC_MESSAGES/messages.po | 150 +++++++------ locales/id/LC_MESSAGES/messages.po | 150 +++++++------ locales/ko/LC_MESSAGES/messages.po | 150 +++++++------ locales/lzh/LC_MESSAGES/messages.po | 150 +++++++------ locales/mk/LC_MESSAGES/messages.po | 150 +++++++------ locales/pl/LC_MESSAGES/messages.po | 150 +++++++------ locales/pt_BR/LC_MESSAGES/messages.po | 155 +++++++------ locales/ro/LC_MESSAGES/messages.po | 150 +++++++------ locales/ru/LC_MESSAGES/messages.po | 155 +++++++------ locales/sai/LC_MESSAGES/messages.po | 150 +++++++------ locales/si/LC_MESSAGES/messages.po | 150 +++++++------ locales/sk/LC_MESSAGES/messages.po | 150 +++++++------ locales/ta/LC_MESSAGES/messages.po | 150 +++++++------ locales/tr/LC_MESSAGES/messages.po | 150 +++++++------ locales/uk/LC_MESSAGES/messages.po | 150 +++++++------ locales/vi/LC_MESSAGES/messages.po | 150 +++++++------ locales/zh_Hans/LC_MESSAGES/messages.po | 154 +++++++------ locales/zh_Hant/LC_MESSAGES/messages.po | 150 +++++++------ 29 files changed, 2375 insertions(+), 2129 deletions(-) diff --git a/locales/ar/LC_MESSAGES/messages.po b/locales/ar/LC_MESSAGES/messages.po index f193ce57f..e316bff09 100644 --- a/locales/ar/LC_MESSAGES/messages.po +++ b/locales/ar/LC_MESSAGES/messages.po @@ -8,11 +8,11 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-19 01:44+0000\n" "Last-Translator: Mohamed Brahimi \n" -"Language-Team: Arabic \n" +"Language-Team: Arabic \n" "Language: ar\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -12320,28 +12320,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12349,7 +12351,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12357,64 +12359,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12422,28 +12424,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12452,22 +12454,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12475,11 +12477,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12488,29 +12490,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12520,7 +12522,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12528,7 +12530,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12536,17 +12538,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12554,39 +12556,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12596,11 +12598,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12609,38 +12611,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12648,7 +12650,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12656,18 +12658,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12676,7 +12678,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12687,7 +12689,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12705,7 +12707,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12714,7 +12716,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12734,17 +12736,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12752,7 +12754,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12760,10 +12762,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/ars/LC_MESSAGES/messages.po b/locales/ars/LC_MESSAGES/messages.po index 28ca798df..3f7c6bcca 100644 --- a/locales/ars/LC_MESSAGES/messages.po +++ b/locales/ars/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/de/LC_MESSAGES/messages.po b/locales/de/LC_MESSAGES/messages.po index 781d47983..e9addebd5 100644 --- a/locales/de/LC_MESSAGES/messages.po +++ b/locales/de/LC_MESSAGES/messages.po @@ -14,11 +14,11 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-17 16:00+0000\n" "Last-Translator: Carsten Gerlach \n" -"Language-Team: German \n" +"Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -12398,28 +12398,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12427,7 +12429,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12435,64 +12437,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12500,28 +12502,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12530,22 +12532,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12553,11 +12555,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12566,29 +12568,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12598,7 +12600,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12606,7 +12608,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12614,17 +12616,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12632,39 +12634,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12674,11 +12676,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12687,38 +12689,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12726,7 +12728,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12734,18 +12736,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12754,7 +12756,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12765,7 +12767,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12783,7 +12785,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12792,7 +12794,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12812,17 +12814,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12830,7 +12832,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12838,10 +12840,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/eo/LC_MESSAGES/messages.po b/locales/eo/LC_MESSAGES/messages.po index 8299f863d..a69a8cf49 100644 --- a/locales/eo/LC_MESSAGES/messages.po +++ b/locales/eo/LC_MESSAGES/messages.po @@ -7,11 +7,11 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-21 12:32+0000\n" "Last-Translator: phlostically \n" -"Language-Team: Esperanto \n" +"Language-Team: Esperanto \n" "Language: eo\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2745,8 +2745,8 @@ msgid "" "to ensure that version query invocations (such as ``pip -V``) run as quickly " "as possible." msgstr "" -"Tiu teĥniko estas speciale utila por komandlinia programo, kies versio-peto (" -"kiel ekzemple ``pip -V``) devas ruliĝi rapide." +"Tiu teĥniko estas speciale utila por komandlinia programo, kies versio-peto " +"(kiel ekzemple ``pip -V``) devas ruliĝi rapide." #: ../source/discussions/versioning.rst:198 msgid "" @@ -3209,8 +3209,8 @@ msgid "" msgstr "" "La :ref:`specifo ` kaj la aro de :term:`Kernaj Metadatenaj " "Kampoj ` difinitaj de ĝi, pri la ĉefaj statikaj " -"atributoj de :term:`Distribua Pako ` aŭ :term:`" -"Instalita Projekto `." +"atributoj de :term:`Distribua Pako ` aŭ :term:" +"`Instalita Projekto `." #: ../source/glossary.rst:74 msgid "Core Metadata Field" @@ -4774,8 +4774,8 @@ msgid "" "completions via the ``--install-completion`` option." msgstr "" "Ĉar ĉi tiu ekzemplo uzas ``typer``, oni povas nun superrigardi la opciojn de " -"la programo per la flago ``--help`` aŭ agordi kompletigadon per la flago " -"``--install-completion``." +"la programo per la flago ``--help`` aŭ agordi kompletigadon per la flago ``--" +"install-completion``." #: ../source/guides/creating-command-line-tools.rst:158 msgid "" @@ -4798,8 +4798,8 @@ msgid "" "an entry point specific to ``pipx run``. The same can be defined as follows " "in :file:`pyproject.toml`:" msgstr "" -"Tamen ekzistas pli praktika solvo de tiu problemo: enirpunkto specifa al ``" -"pipx run``. La sama estas difinebla jene en :file:`pyproject.toml`:" +"Tamen ekzistas pli praktika solvo de tiu problemo: enirpunkto specifa al " +"``pipx run``. La sama estas difinebla jene en :file:`pyproject.toml`:" #: ../source/guides/creating-command-line-tools.rst:177 msgid "" @@ -5356,8 +5356,8 @@ msgid "" "`Distribution ` (aka \":term:`Package `\") for your project." msgstr "" -"Por igi vian projekton instalebla ĉe :term:`Pakindekso ` kiel " -":term:`PyPI `, vi kreu :term:`Distribuon " +"Por igi vian projekton instalebla ĉe :term:`Pakindekso ` " +"kiel :term:`PyPI `, vi kreu :term:`Distribuon " "` (ankaŭ konatan kiel «:term:`pakon `») por via projekto." @@ -6755,8 +6755,8 @@ msgid "" "the standard library's virtual environment tool :ref:`venv` and install " "packages. The guide covers how to:" msgstr "" -"Ĉi tiu estas gvidilo pri kiel krei kaj aktivigi virtualan medion per la ilo " -":ref:`venv` en la norma biblioteko kaj instali pakojn tien. La gvidilo " +"Ĉi tiu estas gvidilo pri kiel krei kaj aktivigi virtualan medion per la ilo :" +"ref:`venv` en la norma biblioteko kaj instali pakojn tien. La gvidilo " "diskutas la jenon:" #: ../source/guides/installing-using-pip-and-virtual-environments.rst:8 @@ -7480,9 +7480,9 @@ msgid "" "otherwise, check the `SPDX license list `__ for the identifier " "that matches the license used in your project." msgstr "" -"En via projekta agorda dosiero, tajpu vian licenco-esprimon sub ``license`` (" -"tabelo ``[project]`` en :file:`pyproject.toml`), aŭ la ekvivalentaĵon de via " -"pakilo. Certigu, ke vi forigis ajnan malnovan subŝlosilojn de tabelo " +"En via projekta agorda dosiero, tajpu vian licenco-esprimon sub ``license`` " +"(tabelo ``[project]`` en :file:`pyproject.toml`), aŭ la ekvivalentaĵon de " +"via pakilo. Certigu, ke vi forigis ajnan malnovan subŝlosilojn de tabelo " "``license`` aŭ klasigilojn ``License ::``. Via ekzistanta valoro por " "``license`` povas jam validi (ekz. ``MIT``, ``Apache-2.0 OR BSD-2-Clause`` " "ktp); alie, vidu la `liston de SPDX-licencoj `__ por la " @@ -7537,9 +7537,9 @@ msgid "" "packaging tool, and make sure to remove any legacy ``license`` table subkeys " "or ``License ::`` classifiers." msgstr "" -"En via projekta agorda dosiero, tajpu vian licenco-esprimon sub ``license`` (" -"tabelo ``[project]`` en :file:`pyproject.toml`), aŭ la ekvivalentaĵon de via " -"pakilo. Certigu, ke vi forigis ajnan malnovan subŝlosilojn de tabelo " +"En via projekta agorda dosiero, tajpu vian licenco-esprimon sub ``license`` " +"(tabelo ``[project]`` en :file:`pyproject.toml`), aŭ la ekvivalentaĵon de " +"via pakilo. Certigu, ke vi forigis ajnan malnovan subŝlosilojn de tabelo " "``license`` aŭ klasigilojn ``License ::``." #: ../source/guides/licensing-examples-and-user-scenarios.rst:326 @@ -8524,8 +8524,8 @@ msgid "" "automatic wrapping with Cython. It also supports performance-oriented Python " "implementations that provide a CPython-like C-API, such as PyPy and Pyston." msgstr "" -"Krom sia utileco por krei akcelilan modulon, `Cython `" -"__ estas ankaŭ vaste uzata por krei volvantan modulon de API en C aŭ C++. " +"Krom sia utileco por krei akcelilan modulon, `Cython `__ estas ankaŭ vaste uzata por krei volvantan modulon de API en C aŭ C++. " "Por tio oni volvas la interfacojn malaŭtomate. Ekzistas multo da libereco " "pri fasonado kaj optimumado de la volvanta kodo. Tamen, tio eble ne estas " "bona elekto por rapide volvi grandegan API. Vidu la `liston de triapartiaj " @@ -10199,10 +10199,9 @@ msgid "" "`virtualenv` (PyPA project) and :doc:`venv ` (part of " "the Python standard library, though missing some features of virtualenv)." msgstr "" -"La normaj iloj por krei kaj uzi virtualan medion malaŭtomate estas " -":ref:`virtualenv` (projekto de PyPA) kaj :doc:`venv ` (" -"parto de la norma biblioteko de Python, sed sen kelkaj funkcioj de " -"virtualenv)." +"La normaj iloj por krei kaj uzi virtualan medion malaŭtomate estas :ref:" +"`virtualenv` (projekto de PyPA) kaj :doc:`venv ` (parto " +"de la norma biblioteko de Python, sed sen kelkaj funkcioj de virtualenv)." #: ../source/guides/tool-recommendations.rst:28 msgid "Installing packages" @@ -10431,9 +10430,9 @@ msgid "" "` in :file:`pyproject.toml`." msgstr "" "La norma ilo por konstrui :term:`fontan distribuon ` kaj :term:`wheel ` alŝuteblajn al PyPI estas :ref:`build`" -". Ĝi rulas la malfasadon :ref:`deklaritan ` en :file:`pyproject.toml`." +"\"sdist\")>` kaj :term:`wheel ` alŝuteblajn al PyPI estas :ref:" +"`build`. Ĝi rulas la malfasadon :ref:`deklaritan ` en :file:`pyproject.toml`." #: ../source/guides/tool-recommendations.rst:130 msgid "" @@ -10750,8 +10749,8 @@ msgstr "" "la uzotan konstruan malfasadon. Ĝi ankaŭ enhavas ŝlosilon ``requires`` " "listigantan dependecojn por konstrui la projekton – tio estas tipe nur la " "pako de la konstrua malfasado,sed ĝi povas enhavi aliajn dependecojn. Vi " -"povas ankaŭ limigi la versiojn, ekzemple ``requires = " -"[\"setuptools >= 61.0\"]``." +"povas ankaŭ limigi la versiojn, ekzemple ``requires = [\"setuptools >= " +"61.0\"]``." #: ../source/guides/writing-pyproject-toml.rst:55 msgid "" @@ -11168,8 +11167,8 @@ msgid "" "with classifiers beginning with ``Private ::``." msgstr "" "Por malhelpi alŝuti pakon al PyPI, uzu la specialan klasigilon ``Private :: " -"Do Not Upload``. PyPI ĉiam malakceptas pakon de klasigilo komenciĝanta per ``" -"Private ::``." +"Do Not Upload``. PyPI ĉiam malakceptas pakon de klasigilo komenciĝanta per " +"``Private ::``." #: ../source/guides/writing-pyproject-toml.rst:436 #: ../source/specifications/pyproject-toml.rst:148 @@ -14244,11 +14243,11 @@ msgstr "" "Laŭ la ĉi-supra paragrafo :ref:`depending-on-a-separate-ecosystem`, kelkaj " "mastrumaj sistemoj havas siajn proprajn pakadministrilojn. Se oni certegas " "pri la celata mastruma sistemo, oni povas dependi rekte de formo kiel `deb " -"`_ (por Debian, Ubuntu ktp.)" -" aŭ `RPM `_ (por Red Hat, " -"Fedora ktp.), kaj uzi tiun indiĝenan pakadministrilon por instalado kaj eĉ " -"disponigo. Oni povas eĉ uzi `FPM `_ por generi kaj deb kaj RPM el la sama fonto." +"`_ (por Debian, Ubuntu " +"ktp.) aŭ `RPM `_ (por Red " +"Hat, Fedora ktp.), kaj uzi tiun indiĝenan pakadministrilon por instalado kaj " +"eĉ disponigo. Oni povas eĉ uzi `FPM `_ por generi kaj deb kaj RPM el la sama fonto." #: ../source/overview.rst:397 msgid "" @@ -14593,9 +14592,9 @@ msgid "" "\"compatibility tags.\" The compatibility tags express the package's basic " "interpreter requirements and are detailed in PEP 425." msgstr "" -"La lastaj tri komponantj de la dosiernomo antaŭ la sufikso nomiĝas «" -"kongruecaj etikedoj». Tiaj etikedoj esprimas la bazajn postulojn de la pako " -"pri interpretilo kaj estas difinitaj en PEP 425." +"La lastaj tri komponantj de la dosiernomo antaŭ la sufikso nomiĝas " +"«kongruecaj etikedoj». Tiaj etikedoj esprimas la bazajn postulojn de la " +"pako pri interpretilo kaj estas difinitaj en PEP 425." #: ../source/specifications/binary-distribution-format.rst:145 msgid "Escaping and Unicode" @@ -14625,9 +14624,9 @@ msgstr "" "LOW LINE kaj FULL STOP) estu anstataŭigita per ``_`` (LOW LINE), kaj " "majuskloj estu anstataŭigitaj per la respondantaj minuskloj. Tio " "ekvivalentas ordinaran :ref:`normigon de nomo ` sekvitan " -"de anstataŭigado de ``-`` per ``_``. Ilo konsumanta wheel devas akcepti ``.``" -" (FULL STOP) kaj majusklojn, ĉar tiuj estis permesataj de malnova versio de " -"ĉi tiu specifo." +"de anstataŭigado de ``-`` per ``_``. Ilo konsumanta wheel devas akcepti ``." +"`` (FULL STOP) kaj majusklojn, ĉar tiuj estis permesataj de malnova versio " +"de ĉi tiu specifo." #: ../source/specifications/binary-distribution-format.rst:157 msgid "" @@ -14677,16 +14676,23 @@ msgid "File contents" msgstr "Dosieraj enhavoj" #: ../source/specifications/binary-distribution-format.rst:177 +#, fuzzy +#| msgid "" +#| "The contents of a wheel file, where {distribution} is replaced with the " +#| "name of the package, e.g. ``beaglevote`` and {version} is replaced with " +#| "its version, e.g. ``1.0.0``, consist of:" msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" "La enhavo de wheel-dosiero, en kiu {distribution} estas anstataŭigita per la " "nomo de la pako, ekz. ``beaglevote``, kaj {version} estas anstataŭigita per " "la versio, ekz. ``1.0.0``, konsistas el la jeno:" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " @@ -14696,18 +14702,18 @@ msgstr "" "``purelib`` aŭ ``platlib`` laŭ la specifo en ``WHEEL``. Kaj ``purelib`` kaj " "``platlib`` estas ofte ``site-packages``." -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "``{distribuo}-{versio}.dist-info/`` enhavas metadatenojn." -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" ":file:`{distribution}-{version}.dist-info/licenses/` enhavas licenco-" "dosierojn." -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -14719,7 +14725,7 @@ msgstr "" "subdosierujo estas indico de vortaro de instalaj dosierlokoj (ekz. ``data``, " "``scripts``, ``headers``, ``purelib``, ``platlib``)." -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -14727,7 +14733,7 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." @@ -14735,7 +14741,7 @@ msgstr "" "``{distribution}-{version}.dist-info/METADATA`` estas metadatenoj de la " "formo Metadatenoj versio 1.1 aŭ pli nova." -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" @@ -14743,11 +14749,11 @@ msgstr "" "``{distribuo}-{versio}.dist-info/WHEEL`` estas metadatenoj pri la arĥivo mem " "en la sama baza formo «ŝlosilo: valoro»::" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "``Wheel-Version`` estas la versia numero de la specifo pri Wheel." -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." @@ -14755,7 +14761,7 @@ msgstr "" "``Generator`` estas la nomo kaj, nedevige, la versio de la programo " "generinta la arĥivon." -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " @@ -14764,7 +14770,7 @@ msgstr "" "``Root-Is-Purelib`` estas vera, se la supranivela dosierujo de la arĥivo " "instaliĝu al purelib, se ne, la radiko instaliĝu al platlib." -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." @@ -14772,14 +14778,14 @@ msgstr "" "``Tag`` estas la pliigitaj kongruecaj etikedoj de la wheel; en la ekzemplo, " "la dosiernomo enhavus ``py2.py3-none-any``." -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" "``Build`` estas la numero de la konstro; ĝi estas preterlasita, se mankas " "numero de la konstruo." -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " @@ -14789,7 +14795,7 @@ msgstr "" "subtenata versio, kaj devas malsukcesi, se ``Wheel-Version`` havas pli " "grandan maĵoran version ol la subtenatan version." -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." @@ -14797,11 +14803,11 @@ msgstr "" "Wheel, estante instaleblaĵon por pluraj versioj de Python, ne ĝenerale " "inkluzivas ``.pyc``-dosierojn." -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "Wheel ne enhavas setup.py aŭ setup.cfg." -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -14809,12 +14815,12 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "La dosierujo .dist-info" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." @@ -14822,7 +14828,7 @@ msgstr "" "La dosierujoj .dist-info de Wheel inkluzivas, minimume, METADATA, WHEEL, kaj " "RECORD." -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." @@ -14830,11 +14836,11 @@ msgstr "" "METADATA estas la pakaj metadatenoj, en la sama formo kiel PKG-INFO en la " "radiko de fontaj distribuoj." -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "WHEEL estas la wheel-metadatenoj specifaj al iu konstruo de la pako." -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -14849,19 +14855,19 @@ msgstr "" "ĉar subskribita wheel-dosiero dependas de la fortikaj haketaĵoj en RECORD " "por la integrecon de la arĥivo." -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" "La INSTALLER kaj REQUESTED de PEP 376 ne estas inkluzivitaj en la arĥivo." -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" "RECORD.jws estas uzataj por ciferecaj subskriboj. Ĝi ne estas menciita en " "RECORD." -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." @@ -14869,7 +14875,7 @@ msgstr "" "RECORD.p7s estas permesata por tiuj, kiuj preferas uzi S/MIME-subskribon por " "sekurigi wheel-dosieron. Ĝi ne menciiĝas en RECORD." -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -14877,11 +14883,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "La dosierujo :file:`.dist-info/licenses/`" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -14890,11 +14896,11 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "La dosierujo .data" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " @@ -14903,7 +14909,7 @@ msgstr "" "Iu ajn dosiero ne ordinare instalita al site-packages iras en la dosierujon ." "data, nomitan kiel la dosierujon .dist-info sed kun la sufikso .data/::" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " @@ -14913,11 +14919,11 @@ msgstr "" "dokumentoj ktp de la distribuo. Dum instalado, la enhavoj de tiuj " "dosierujoj kopiiĝas al siaj celaj dosierlokoj." -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "Subskribitaj wheel-dosieroj" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -14927,7 +14933,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -14939,7 +14945,7 @@ msgstr "" "la arĥivo devas havi ĝustan haketaĵon en RECORD; se ne, la instalado " "malsukcesos." -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -14947,11 +14953,11 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "(La haketaĵa valoro estas la sama formo uzata en RECORD.)" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." @@ -14959,7 +14965,7 @@ msgstr "" "Se RECORD.p7s estas uzata, ĝi devas enhavi malligitan S/MIME-forman " "subskribon de RECORD." -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -14967,15 +14973,15 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "Vidu" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "https://datatracker.ietf.org/doc/html/rfc7515" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" @@ -14983,26 +14989,26 @@ msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "https://datatracker.ietf.org/doc/html/rfc7517" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "Oftaj demandoj" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "Wheel difinas dosierujon .data. Ĉu mi metu ĉiom da miaj datenoj tien?" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -15012,11 +15018,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "Kial wheel inkluzivas alkroĉitajn subskribojn?" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -15029,22 +15035,22 @@ msgstr "" "subskribitaj, la arĥivo estas redensigebla sen eksvalidigi la subskribon, " "kaj individuaj dosieroj estas kontroleblaj sen reelŝutado de la tuta arĥivo." -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "Kial wheel permesas JWS-subskribojn?" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "Kial wheel ankaŭ permesas S/MIME-subskribojn?" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." @@ -15052,7 +15058,7 @@ msgstr "" "S/MIME-subskribo estas permesata por tiuj uzantoj, kiuj devas aŭ volas uzi " "ekzistantan publikŝlosilan infrastrukturon kun wheel." -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." @@ -15060,11 +15066,11 @@ msgstr "" "Subskribita pako estas nur baza briko de sekura pako-ĝisdatiga sistemo. " "Wheel nur provizas la bazan brikon." -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "Kio temas pri «purelib» kontraste kun «platlib»?" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -15076,7 +15082,7 @@ msgstr "" "lib/pythonX.Y/site-packages» kaj platformo-dependajn pakojn al «/usr/lib64/" "pythonX.Y/site-packages»." -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -15084,18 +15090,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "Ĉu eblas importi Python-kodon rekte el wheel-dosiero?" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -15104,7 +15110,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -15115,7 +15121,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -15145,7 +15151,7 @@ msgstr "" "ĝuste uzas la abstraktajn rimedajn API-ojn interne, interagado kun eksteraj " "komponantoj povas postuli realan surdiskan dosieron." -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -15154,7 +15160,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -15174,11 +15180,11 @@ msgstr "" msgid "History" msgstr "Historio" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "Februaro 2013: Ĉi tiu specifo estis aprobita per :pep:`427`." -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." @@ -15186,7 +15192,7 @@ msgstr "" "Februaro 2021: La reguloj pri kodŝanĝado en wheel-dosiernomoj estis " "reviziitaj konforme al la fakta konduto de popularaj iloj." -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -15198,7 +15204,7 @@ msgstr "" "simbola ligilo aŭ subdosierujo en tiu dosierujo; tial kondutoj povas " "diferenci inter iloj)." -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -15208,10 +15214,16 @@ msgstr "" "per :pep:`639`." #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "Apendico" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "Ekzempla realigo de urlsafe-base64-nopad::" @@ -16142,8 +16154,8 @@ msgid "" "in :doc:`version-specifiers`. The distribution's version number will be " "implied if none is specified." msgstr "" -"Oni povas provizi versio-deklaron, kiu devas observi la regulojn en :doc" -":`version-specifiers`. Se nenio estas provizita, tio implicas la versian " +"Oni povas provizi versio-deklaron, kiu devas observi la regulojn en :doc:" +"`version-specifiers`. Se nenio estas provizita, tio implicas la versian " "numeron de la distribuo." #: ../source/specifications/core-metadata.rst:769 @@ -17885,8 +17897,8 @@ msgstr "" "la malferma rekta krampo, inter la ekstraĵaj nomoj kaj la apartigantaj " "kvadrataj krampoj kaj dupunktoj, kaj post la ferma rekta krampo. La sintakso " "de ekstraĵoj estas formale specifita kiel parto de :pep:`508` (kiel " -"``extras``), kaj restriktoj pri valoroj estas formale specifitaj en " -":pep:`685`. Ilo skribanta la dosieron metu spaceton nur inter la objekta " +"``extras``), kaj restriktoj pri valoroj estas formale specifitaj en :pep:" +"`685`. Ilo skribanta la dosieron metu spaceton nur inter la objekta " "referenco kaj la malferma rekta krampo." #: ../source/specifications/entry-points.rst:128 @@ -18194,9 +18206,9 @@ msgid "" "manager." msgstr "" "Due, ĝi reguligas, ke dum instalado de pako al la malloka kunteksto de " -"interpretilo (aŭ al nemarkita interpretilo, aŭ se oni superregas la markadon)" -", **Python -specifa pakadministrilo modifu aŭ forviŝu dosierojn nur en la " -"dosierujoj de la sysconfig-skemo, en kiu ĝi kreus la dosierojn**. Tio " +"interpretilo (aŭ al nemarkita interpretilo, aŭ se oni superregas la " +"markadon), **Python -specifa pakadministrilo modifu aŭ forviŝu dosierojn nur " +"en la dosierujoj de la sysconfig-skemo, en kiu ĝi kreus la dosierojn**. Tio " "permesas al distribuanto de Python-interpretilo starigi du dosierujojn – unu " "por siaj propre mastrumataj pakoj, la alia por nemastrumataj pakoj " "instalitaj de la uzanto –, certigante, ke instalado de nemastrumata pako ne " @@ -19406,9 +19418,9 @@ msgid "" "{platform tag}.whl``. Other package formats may have their own conventions." msgstr "" "La konstruita pakformo ``wheel`` inkluzivas tiujn etikedojn en dosiernomoj " -"laŭ la formo " -"``{distribuo}-{versio}(-{konstruetikedo})?-{pythonetikedo}-{abietikedo}-{platformetikedo}.whl``" -". Alia pakformo povas havi sian propran konvencion." +"laŭ la formo ``{distribuo}-{versio}(-{konstruetikedo})?-{pythonetikedo}-" +"{abietikedo}-{platformetikedo}.whl``. Alia pakformo povas havi sian propran " +"konvencion." #: ../source/specifications/platform-compatibility-tags.rst:33 msgid "Any potential spaces in any tag should be replaced with ``_``." @@ -20821,10 +20833,10 @@ msgid "" "table, as they would be ambiguous in the face of ``[project.scripts]`` and " "``[project.gui-scripts]``, respectively." msgstr "" -"Konstrua malfasado DEVAS sciigi pri eraro, se la metadatenoj difinas ``" -"[project.entry-points.console_scripts]`` aŭ ``" -"[project.entry-points.gui_scripts]``, ĉar tiuj estus ambiguaj pro ``" -"[project.scripts]`` kaj ``[project.gui-scripts]``, respektive." +"Konstrua malfasado DEVAS sciigi pri eraro, se la metadatenoj difinas " +"``[project.entry-points.console_scripts]`` aŭ ``[project.entry-points." +"gui_scripts]``, ĉar tiuj estus ambiguaj pro ``[project.scripts]`` kaj " +"``[project.gui-scripts]``, respektive." #: ../source/specifications/pyproject-toml.rst:422 msgid "" @@ -21556,8 +21568,8 @@ msgid "" "NOT** rely on this redirection and **MUST** request the normalized URL." msgstr "" "Deponejo **POVAS** redirekti nenormigitan retadreson al la kanona normigita " -"retadreso (ekz. de ``/Foobar/`` al ``/foobar/``). Tamen, kliento **DEVAS NE**" -" dependi de tia redirektado kaj **DEVAS** peti la normigitan retadreson." +"retadreso (ekz. de ``/Foobar/`` al ``/foobar/``). Tamen, kliento **DEVAS " +"NE** dependi de tia redirektado kaj **DEVAS** peti la normigitan retadreson." #: ../source/specifications/simple-repository-api.rst:73 msgid "" @@ -22557,8 +22569,8 @@ msgstr "" "specifo postulas, ke servilo ĉiam inkluzivu ĉapon``Content-Type`` pri la " "enhavtipo de la respondo. Tio estas teĥnike ne retrokongrua ŝanĝo. Tamen " "praktike `pip devigas ĉi tiun postulon `_. Tial la risko de reala rompo estas malgranda." +"cf3696a81b341925f82f20cb527e656176987565/src/pip/_internal/index/collector." +"py#L123-L150>`_. Tial la risko de reala rompo estas malgranda." #: ../source/specifications/simple-repository-api.rst:673 msgid "An example of how a client can operate would look like:" @@ -24000,8 +24012,8 @@ msgstr "" "necees, se projekto *ŝanĝas* la manieron de versia numerado tiel, ke la " "ordinaraj reguloj pri ordigado de versioj estas malĝustaj. Ekzemple, se " "projekto uzas dato-bazajn versiojn kiel ``2014.04`` kaj volas ŝanĝi al " -"semantikaj versioj kiel ``1.0``, do la novaj eldonoj estus rigardataj kiel *" -"pli malnovaj* ol la dato-bazaj eldonoj laŭ la ordinara ordigado::" +"semantikaj versioj kiel ``1.0``, do la novaj eldonoj estus rigardataj kiel " +"*pli malnovaj* ol la dato-bazaj eldonoj laŭ la ordinara ordigado::" #: ../source/specifications/version-specifiers.rst:384 msgid "" diff --git a/locales/es/LC_MESSAGES/messages.po b/locales/es/LC_MESSAGES/messages.po index bee29480f..157caa8b8 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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-11-24 22:33+0000\n" "Last-Translator: gallegonovato \n" "Language-Team: Spanish ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12641,7 +12643,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12649,64 +12651,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12714,28 +12716,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12744,22 +12746,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12767,11 +12769,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12780,29 +12782,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12812,7 +12814,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12820,7 +12822,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12828,17 +12830,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12846,39 +12848,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12888,11 +12890,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12901,38 +12903,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12940,7 +12942,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12948,18 +12950,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12968,7 +12970,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12979,7 +12981,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12997,7 +12999,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -13006,7 +13008,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -13026,17 +13028,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -13044,7 +13046,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -13052,10 +13054,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/fa/LC_MESSAGES/messages.po b/locales/fa/LC_MESSAGES/messages.po index 7f1c95fab..9803c0f64 100644 --- a/locales/fa/LC_MESSAGES/messages.po +++ b/locales/fa/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2023-02-15 07:52+0000\n" "Last-Translator: Arsalan Dehghani \n" "Language-Team: Persian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12369,7 +12371,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12377,64 +12379,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12442,28 +12444,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12472,22 +12474,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12495,11 +12497,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12508,29 +12510,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12540,7 +12542,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12548,7 +12550,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12556,17 +12558,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12574,39 +12576,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12616,11 +12618,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12629,38 +12631,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12668,7 +12670,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12676,18 +12678,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12696,7 +12698,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12707,7 +12709,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12725,7 +12727,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12734,7 +12736,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12754,17 +12756,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12772,7 +12774,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12780,10 +12782,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/fil/LC_MESSAGES/messages.po b/locales/fil/LC_MESSAGES/messages.po index 8e7046f18..3ca8abfef 100644 --- a/locales/fil/LC_MESSAGES/messages.po +++ b/locales/fil/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2022-11-19 08:28+0000\n" "Last-Translator: RedFurrFox \n" "Language-Team: Filipino ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12349,7 +12351,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12357,64 +12359,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12422,28 +12424,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12452,22 +12454,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12475,11 +12477,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12488,29 +12490,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12520,7 +12522,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12528,7 +12530,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12536,17 +12538,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12554,39 +12556,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12596,11 +12598,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12609,38 +12611,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12648,7 +12650,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12656,18 +12658,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12676,7 +12678,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12687,7 +12689,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12705,7 +12707,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12714,7 +12716,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12734,17 +12736,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12752,7 +12754,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12760,10 +12762,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/fr/LC_MESSAGES/messages.po b/locales/fr/LC_MESSAGES/messages.po index 09df41023..ee014d21e 100644 --- a/locales/fr/LC_MESSAGES/messages.po +++ b/locales/fr/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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-12-25 20:00+0000\n" "Last-Translator: Laurent FAVOLE \n" "Language-Team: French ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12717,7 +12719,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12725,64 +12727,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12790,28 +12792,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12820,22 +12822,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12843,11 +12845,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12856,29 +12858,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12888,7 +12890,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12896,7 +12898,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12904,17 +12906,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12922,15 +12924,15 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "Voir" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "https://datatracker.ietf.org/doc/html/rfc7515" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" @@ -12938,26 +12940,26 @@ msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "https://datatracker.ietf.org/doc/html/rfc7517" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "Foire aux questions" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12967,11 +12969,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12980,38 +12982,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -13019,7 +13021,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -13027,18 +13029,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -13047,7 +13049,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -13058,7 +13060,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -13076,7 +13078,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -13085,7 +13087,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -13105,17 +13107,17 @@ msgstr "" msgid "History" msgstr "Historique" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -13123,7 +13125,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 #, fuzzy #| msgid "March 2001: Core metadata 1.0 was approved through :pep:`241`." @@ -13135,10 +13137,16 @@ msgstr "" "`241`." #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "Annexe" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/frc/LC_MESSAGES/messages.po b/locales/frc/LC_MESSAGES/messages.po index 5142e3e77..a588497ad 100644 --- a/locales/frc/LC_MESSAGES/messages.po +++ b/locales/frc/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/gl/LC_MESSAGES/messages.po b/locales/gl/LC_MESSAGES/messages.po index 944a196da..aae0655d7 100644 --- a/locales/gl/LC_MESSAGES/messages.po +++ b/locales/gl/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/gmh/LC_MESSAGES/messages.po b/locales/gmh/LC_MESSAGES/messages.po index 28fed5b4d..f56470ad9 100644 --- a/locales/gmh/LC_MESSAGES/messages.po +++ b/locales/gmh/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/hi/LC_MESSAGES/messages.po b/locales/hi/LC_MESSAGES/messages.po index 8b98a8f90..48b18171f 100644 --- a/locales/hi/LC_MESSAGES/messages.po +++ b/locales/hi/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-09-16 10:09+0000\n" "Last-Translator: kumar Shivam \n" "Language-Team: Hindi ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12399,7 +12401,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12407,64 +12409,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12472,28 +12474,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12502,22 +12504,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12525,11 +12527,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12538,29 +12540,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12570,7 +12572,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12578,7 +12580,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12586,17 +12588,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12604,39 +12606,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12646,11 +12648,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12659,38 +12661,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12698,7 +12700,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12706,18 +12708,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12726,7 +12728,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12737,7 +12739,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12755,7 +12757,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12764,7 +12766,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12784,17 +12786,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12802,7 +12804,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12810,10 +12812,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/id/LC_MESSAGES/messages.po b/locales/id/LC_MESSAGES/messages.po index 42014fcfe..505be2259 100644 --- a/locales/id/LC_MESSAGES/messages.po +++ b/locales/id/LC_MESSAGES/messages.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-10-17 21:16+0000\n" "Last-Translator: oon arfiandwi \n" "Language-Team: Indonesian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12405,7 +12407,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12413,64 +12415,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12478,28 +12480,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12508,22 +12510,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12531,11 +12533,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12544,29 +12546,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12576,7 +12578,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12584,7 +12586,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12592,17 +12594,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12610,39 +12612,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12652,11 +12654,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12665,38 +12667,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12704,7 +12706,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12712,18 +12714,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12732,7 +12734,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12743,7 +12745,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12761,7 +12763,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12770,7 +12772,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12790,17 +12792,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12808,7 +12810,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12816,10 +12818,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index a28c5db10..9c8f24153 100644 --- a/locales/ko/LC_MESSAGES/messages.po +++ b/locales/ko/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-11-03 06:00+0000\n" "Last-Translator: 황인아 \n" "Language-Team: Korean ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12441,7 +12443,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12449,64 +12451,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12514,28 +12516,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12544,22 +12546,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12567,11 +12569,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12580,29 +12582,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12612,7 +12614,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12620,7 +12622,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12628,17 +12630,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12646,39 +12648,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12688,11 +12690,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12701,38 +12703,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12740,7 +12742,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12748,18 +12750,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12768,7 +12770,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12779,7 +12781,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12797,7 +12799,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12806,7 +12808,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12826,17 +12828,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12844,7 +12846,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12852,10 +12854,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/lzh/LC_MESSAGES/messages.po b/locales/lzh/LC_MESSAGES/messages.po index bd48fac8e..3fbee95c1 100644 --- a/locales/lzh/LC_MESSAGES/messages.po +++ b/locales/lzh/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-01-31 06:01+0000\n" "Last-Translator: maker \n" "Language-Team: Chinese (Literary) ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12349,7 +12351,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12357,64 +12359,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12422,28 +12424,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12452,22 +12454,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12475,11 +12477,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12488,29 +12490,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12520,7 +12522,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12528,7 +12530,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12536,17 +12538,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12554,39 +12556,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12596,11 +12598,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12609,38 +12611,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12648,7 +12650,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12656,18 +12658,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12676,7 +12678,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12687,7 +12689,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12705,7 +12707,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12714,7 +12716,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12734,17 +12736,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12752,7 +12754,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12760,10 +12762,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/mk/LC_MESSAGES/messages.po b/locales/mk/LC_MESSAGES/messages.po index 778284401..7fd79df9f 100644 --- a/locales/mk/LC_MESSAGES/messages.po +++ b/locales/mk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2023-10-21 04:04+0000\n" "Last-Translator: \"Kristijan \\\"Fremen\\\" Velkovski\" \n" "Language-Team: Macedonian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12353,7 +12355,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12361,64 +12363,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12426,28 +12428,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12456,22 +12458,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12479,11 +12481,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12492,29 +12494,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12524,7 +12526,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12532,7 +12534,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12540,17 +12542,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12558,39 +12560,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12600,11 +12602,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12613,38 +12615,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12652,7 +12654,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12660,18 +12662,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12680,7 +12682,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12691,7 +12693,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12709,7 +12711,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12718,7 +12720,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12738,17 +12740,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12756,7 +12758,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12764,10 +12766,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/pl/LC_MESSAGES/messages.po b/locales/pl/LC_MESSAGES/messages.po index e5063507e..6f4880010 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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/pt_BR/LC_MESSAGES/messages.po b/locales/pt_BR/LC_MESSAGES/messages.po index 7068d81f2..9ceb1187f 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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-16 14:00+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Portuguese (Brazil) ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" "O conteúdo de um arquivo wheel, onde {distribution} é substituído pelo nome " "do pacote, por exemplo, ``beaglevote`` e {version} é substituído por sua " "versão, p.ex., ``1.0.0``, consiste em:" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " @@ -16237,18 +16244,18 @@ msgstr "" "``purelib`` ou ``platlib`` conforme especificado em ``WHEEL``. ``purelib`` e " "``platlib`` são normalmente ``site-packages``." -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "``{distribution}-{version}.dist-info/`` contém metadados." -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 #, fuzzy #| msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "``{distribution}-{version}.dist-info/`` contém metadados." -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -16260,7 +16267,7 @@ msgstr "" "subdiretório é um índice em um dicionário de caminhos de instalação (p.ex., " "``data``, ``scripts``, ``headers``, ``purelib``, ``platlib``)." -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 #, fuzzy #| msgid "" #| "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" @@ -16277,7 +16284,7 @@ msgstr "" "python`` no momento da instalação. Eles podem ter qualquer ou nenhuma " "extensão." -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." @@ -16285,7 +16292,7 @@ msgstr "" "``{distribution}-{version}.dist-info/METADATA`` é Metadata versão 1.1 ou " "metadados de formato superior." -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" @@ -16293,11 +16300,11 @@ msgstr "" "``{distribution}-{version}.dist-info/WHEEL`` são metadados sobre p arquivo " "em si no mesmo formato \"chave: valor\"::" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "``Wheel-Version`` é o número de versão da especificação Wheel." -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." @@ -16305,7 +16312,7 @@ msgstr "" "``Generator`` é o nome e, opcionalmente, a versão do software que produziu o " "arquivo." -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " @@ -16315,7 +16322,7 @@ msgstr "" "deve ser instalado em purelib; caso contrário, a raiz deve ser instalada no " "platlib." -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." @@ -16323,14 +16330,14 @@ msgstr "" "``Tag`` são as tags de compatibilidade expandida do wheel; no exemplo, o " "nome do arquivo conteria ``py2.py3-none-any``." -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" "``Build`` é o número da construção e é omitido se não houver número da " "construção." -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " @@ -16340,7 +16347,7 @@ msgstr "" "que ele suporta, e deve falhar se Wheel-Version tiver uma versão principal " "maior do que a versão que ele suporta." -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." @@ -16348,11 +16355,11 @@ msgstr "" "O Wheel, sendo um formato de instalação destinado a funcionar em várias " "versões do Python, geralmente não inclui arquivos .pyc." -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "Wheel não contém setup.py ou setup.cfg." -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -16364,12 +16371,12 @@ msgstr "" "oferece um superconjunto da funcionalidade fornecida pelos formatos binários " "wininst e egg existentes." -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "O diretório .dist-info" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." @@ -16377,7 +16384,7 @@ msgstr "" "Os diretórios .dist-info de wheels incluem no mínimo METADATA, WHEEL e " "RECORD." -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." @@ -16385,12 +16392,12 @@ msgstr "" "METADATA são os metadados do pacote, o mesmo formato do PKG-INFO encontrado " "na raiz dos sdists." -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" "WHEEL são os metadados de wheel específicos para uma construção do pacote." -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -16405,17 +16412,17 @@ msgstr "" "wheel assinados contam com hashes fortes em RECORD para validar a " "integridade do arquivo." -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "INSTALLER e REQUESTED da PEP 376 não são incluídos no arquivo." -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" "RECORD.jws é usado para assinaturas digitais. Não é mencionado no RECORD." -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." @@ -16424,7 +16431,7 @@ msgstr "" "assinaturas S/MIME para proteger seus arquivos wheels. Não é mencionado no " "RECORD." -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -16436,13 +16443,13 @@ msgstr "" "a instalação falhará se qualquer arquivo no arquivo não for mencionado e com " "hash correto em RECORD." -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 #, fuzzy #| msgid "The .dist-info directory" msgid "The :file:`.dist-info/licenses/` directory" msgstr "O diretório .dist-info" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -16451,11 +16458,11 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "O diretório .data" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " @@ -16465,7 +16472,7 @@ msgstr "" "para o diretório .data, nomeado como o diretório .dist-info, mas com a " "extensão .data/::" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " @@ -16475,11 +16482,11 @@ msgstr "" "documentação e assim por diante da distribuição. Durante a instalação, o " "conteúdo desses subdiretórios é movido para seus caminhos de destino." -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "Arquivos wheels assinados" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -16496,7 +16503,7 @@ msgstr "" "gerados, como arquivos .pyc, mas não RECORD, que não pode conter seu próprio " "hash. Por exemplo::" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -16508,7 +16515,7 @@ msgstr "" "outros arquivos no arquivo devem ter um hash correto em RECORD ou a " "instalação falhará." -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 #, fuzzy msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " @@ -16521,11 +16528,11 @@ msgstr "" "jws adjacente a RECORD. JWS é usado para assinar RECORD incluindo o hash " "SHA-256 de RECORD como a carga JSON da assinatura::" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "(O valor hash é o mesmo formato usado em RECORD.)" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." @@ -16533,7 +16540,7 @@ msgstr "" "Se RECORD.p7s for usado, ele deve conter uma assinatura de formato S/MIME " "separada de RECORD." -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -16546,15 +16553,15 @@ msgstr "" "RECORD, um verificador de assinatura separado só precisa estabelecer se " "RECORD corresponde à assinatura." -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "Veja" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "https://datatracker.ietf.org/doc/html/rfc7515" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" @@ -16562,26 +16569,26 @@ msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "https://datatracker.ietf.org/doc/html/rfc7517" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "FAQ" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "Wheel define um diretório .data. Devo colocar todos os meus dados lá?" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -16597,11 +16604,11 @@ msgstr "" "resource)`` ainda que *esses* arquivos normalmente não sejam distribuídos no " "diretório ``.data`` do *wheel*." -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "Por que o wheel inclui assinaturas anexadas?" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -16615,11 +16622,11 @@ msgstr "" "os arquivos individuais podem ser verificados sem ter que baixar todo o " "arquivo." -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "Por que wheel permite assinaturas JWS?" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " @@ -16630,11 +16637,11 @@ msgstr "" "do projeto da roda. O JWS produz uma implementação puro Python concisa e " "útil." -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "Por que wheel também permite assinaturas S/MIME?" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." @@ -16642,7 +16649,7 @@ msgstr "" "Assinaturas S/MIME são permitidas para usuários que precisam ou querem usar " "uma infraestrutura de chaves públicas existente com o wheel." -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." @@ -16650,11 +16657,11 @@ msgstr "" "Pacotes assinados são apenas um bloco de construção básico em um sistema de " "atualização segura de pacotes. Wheel só fornece o bloco de construção." -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "Qual é a diferença entre \"purelib\" e \"platlib\"?" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -16666,7 +16673,7 @@ msgstr "" "puro Python em '/usr/lib/pythonX.Y/site-packages' e pacotes dependentes de " "plataforma em '/usr/lib64/pythonX.Y/site-packages'." -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -16678,7 +16685,7 @@ msgstr "" "Purelib: true\" com os mesmos arquivos na raiz, e é válido ter arquivos nas " "categorias \"purelib\" e \"platlib\"." -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " @@ -16688,11 +16695,11 @@ msgstr "" "dependendo se é puro Python ou não e esses arquivos devem estar na raiz com " "a configuração apropriada fornecida para \"Root-is-purelib\"." -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "É possível importar código Python diretamente de um arquivo wheel?" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -16706,7 +16713,7 @@ msgstr "" "``sys.path``. No entanto, embora esse comportamento seja uma consequência " "natural do design do formato, não é recomendável confiar nele." -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -16725,7 +16732,7 @@ msgstr "" "segurança, ou integração completa com o maquinário de construção padrão para " "extensões C, publicando arquivos de cabeçalho no local apropriado)." -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -16759,7 +16766,7 @@ msgstr "" "abstratos internamente, a interface com componentes externos ainda pode " "exigir a disponibilidade de um arquivo real no disco." -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -16773,7 +16780,7 @@ msgstr "" "esteja ciente de que muitos projetos exigirão que uma falha seja reproduzida " "com um pacote totalmente instalado antes de aceitá-lo como um bug genuíno." -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -16793,11 +16800,11 @@ msgstr "" msgid "History" msgstr "Histórico" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 #, fuzzy msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " @@ -16807,7 +16814,7 @@ msgstr "" "para alinhá-las com o que as ferramentas populares realmente fazem " "(fevereiro de 2021)." -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -16815,7 +16822,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 #, fuzzy #| msgid "" @@ -16829,10 +16836,16 @@ msgstr "" "conforme originalmente especificado na :pep:`508`." #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "Apêndice" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "Exemplo de implementação de urlsafe-base64-nopad::" diff --git a/locales/ro/LC_MESSAGES/messages.po b/locales/ro/LC_MESSAGES/messages.po index ce878a7d1..11a04f1d6 100644 --- a/locales/ro/LC_MESSAGES/messages.po +++ b/locales/ro/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2021-08-20 01:32+0000\n" "Last-Translator: GUILHERME FERNANDES NETO \n" "Language-Team: Romanian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12351,7 +12353,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12359,64 +12361,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12424,28 +12426,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12454,22 +12456,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12477,11 +12479,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12490,29 +12492,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12522,7 +12524,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12530,7 +12532,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12538,17 +12540,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12556,39 +12558,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12598,11 +12600,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12611,38 +12613,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12650,7 +12652,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12658,18 +12660,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12678,7 +12680,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12689,7 +12691,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12707,7 +12709,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12716,7 +12718,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12736,17 +12738,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12754,7 +12756,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12762,10 +12764,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/ru/LC_MESSAGES/messages.po b/locales/ru/LC_MESSAGES/messages.po index f3ab5c3ba..758e896e6 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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-07-15 14:09+0000\n" "Last-Translator: gfbdrgng \n" "Language-Team: Russian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" "Содержимое файла wheel, в котором {distribution} заменяется именем пакета, " "например ``beaglevote``, а {version} заменяется его версией, например " "``1.0.0``, состоит из:" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " @@ -16201,18 +16208,18 @@ msgstr "" "``purelib`` или ``platlib``, как указано в ``WHEEL``. ``purelib`` и " "``platlib`` обычно являются ``сайт-пакетами``." -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "``{distribution}-{version}.dist-info/`` содержит метаданные." -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 #, fuzzy #| msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "``{distribution}-{version}.dist-info/`` содержит метаданные." -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -16224,7 +16231,7 @@ msgstr "" "является индексом в словаре путей установки (например, ``data``, ``cripts``, " "``headers``, ``purelib``, ``platlib``)." -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 #, fuzzy msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" @@ -16236,7 +16243,7 @@ msgstr "" "чтобы во время установки можно было сгенерировать обертку скрипта и " "переписать ``#!python``. Они могут иметь любое расширение или не иметь его." -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." @@ -16244,7 +16251,7 @@ msgstr "" "``{distribution}-{version}.dist-info/METADATA`` - это метаданные формата " "Metadata версии 1.1 или выше." -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" @@ -16252,18 +16259,18 @@ msgstr "" "``{distribution}-{version}.dist-info/WHEEL`` - это метаданные о самом архиве " "в том же базовом формате key: value::" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "``Wheel-Version`` - это номер версии спецификации Wheel." -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" "``Генератор`` - это имя и, опционально, версия программы, создавшей архив." -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " @@ -16273,7 +16280,7 @@ msgstr "" "должен быть установлен в purelib; в противном случае корень должен быть " "установлен в platlib." -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." @@ -16281,13 +16288,13 @@ msgstr "" "``Tag`` - это расширенные теги совместимости колеса; в примере имя файла " "будет содержать ``py2.py3-none-any``." -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" "``Build`` - это номер сборки и опускается, если номер сборки отсутствует." -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " @@ -16297,7 +16304,7 @@ msgstr "" "чем поддерживаемая ею версия, и должна выходить из строя, если Wheel-Version " "имеет большую мажорную версию, чем поддерживаемая ею версия." -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." @@ -16305,11 +16312,11 @@ msgstr "" "Wheel, будучи форматом установки, предназначенным для работы с несколькими " "версиями Python, обычно не включает файлы .pyc." -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "Колесо не содержит setup.py или setup.cfg." -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -16321,12 +16328,12 @@ msgstr "" "супернабор функций, предоставляемых существующими бинарными форматами " "wininst и egg." -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "Директория .dist-info" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." @@ -16334,7 +16341,7 @@ msgstr "" "Каталоги Wheel .dist-info включают в себя как минимум METADATA, WHEEL и " "RECORD." -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." @@ -16342,11 +16349,11 @@ msgstr "" "METADATA - это метаданные пакета, в том же формате, что и PKG-INFO, которые " "находятся в корне sdists." -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "WHEEL - это метаданные колеса, специфичные для сборки пакета." -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -16361,17 +16368,17 @@ msgstr "" "подписанные файлы колеса полагаются на надежные хэши в RECORD для " "подтверждения целостности архива." -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "В архив не включены файлы PEP 376 \"INSTALLER\" и \"REQUESTED\"." -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" "RECORD.jws используется для цифровых подписей. Он не упоминается в RECORD." -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." @@ -16380,7 +16387,7 @@ msgstr "" "использовать подписи S/MIME для защиты своих колесных файлов. Она не " "упоминается в RECORD." -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -16392,13 +16399,13 @@ msgstr "" "неудачей, если какой-либо файл в архиве не упомянут и не захеширован " "правильно в RECORD." -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 #, fuzzy #| msgid "The .dist-info directory" msgid "The :file:`.dist-info/licenses/` directory" msgstr "Директория .dist-info" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -16407,11 +16414,11 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "Директория .data" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " @@ -16421,7 +16428,7 @@ msgstr "" "помещаются в каталог .data, названный так же, как и каталог .dist-info, но с " "расширением .data/::" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " @@ -16431,11 +16438,11 @@ msgstr "" "и прочим из дистрибутива. Во время установки содержимое этих подкаталогов " "переносится на путь назначения." -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "Подписанные файлы колес" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -16452,7 +16459,7 @@ msgstr "" "файлы, такие как файлы .pyc, но не RECORD, который не может содержать свой " "собственный хеш. Например::" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -16464,7 +16471,7 @@ msgstr "" "остальные файлы в архиве должны иметь правильный хэш в RECORD, иначе " "установка завершится неудачей." -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -16476,11 +16483,11 @@ msgstr "" "примыкающем к RECORD. JWS используется для подписи RECORD путем включения " "SHA-256 хэша RECORD в качестве полезной нагрузки JSON подписи:" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "(Хеш-значение имеет тот же формат, что и в RECORD)" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." @@ -16488,7 +16495,7 @@ msgstr "" "Если используется файл RECORD.p7s, он должен содержать отделенную подпись " "RECORD в формате S/MIME." -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -16500,15 +16507,15 @@ msgstr "" "установки сверяет хэши файлов с RECORD, отдельному средству проверки подписи " "достаточно убедиться, что RECORD соответствует подписи." -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "Смотрите" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "https://datatracker.ietf.org/doc/html/rfc7515" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" @@ -16516,27 +16523,27 @@ msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "https://datatracker.ietf.org/doc/html/rfc7517" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "ЧаВо" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" "Wheel определяет каталог .data. Должен ли я поместить туда все свои данные?" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -16552,11 +16559,11 @@ msgstr "" "если *эти* файлы обычно не будут распространяться в директории *wheel'а* ``." "data``." -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "Почему колесо включает в себя прикрепленные подписи?" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -16569,11 +16576,11 @@ msgstr "" "файлы, архив можно перекомпрессировать, не аннулируя подпись, или проверить " "отдельные файлы без необходимости загружать весь архив." -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "Почему колесо разрешает подписи JWS?" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " @@ -16583,11 +16590,11 @@ msgstr "" "реализации, что также является одной из основных целей дизайна Wheel. JWS " "представляет собой полезную и лаконичную реализацию на чистом Python." -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "Почему wheel также позволяет использовать подписи S/MIME?" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." @@ -16595,7 +16602,7 @@ msgstr "" "Подписи S/MIME разрешены для пользователей, которым необходимо или хочется " "использовать существующую инфраструктуру открытых ключей с помощью колеса." -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." @@ -16603,11 +16610,11 @@ msgstr "" "Подписанные пакеты являются лишь базовым элементом системы безопасного " "обновления пакетов. Wheel предоставляет только строительный блок." -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "Как обстоят дела с \"purelib\" и \"platlib\"?" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -16619,7 +16626,7 @@ msgstr "" "usr/lib/pythonX.Y/site-packages', а платформозависимые пакеты - в '/usr/" "lib64/pythonX.Y/site-packages'." -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -16631,7 +16638,7 @@ msgstr "" "теми же файлами в корне, и законно иметь файлы как в категории \"purelib\", " "так и в категории \"platlib\"." -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " @@ -16642,11 +16649,11 @@ msgstr "" "должны находиться в корне с соответствующей настройкой для \"Root-is-" "purelib\"." -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "Можно ли импортировать код Python непосредственно из файла wheel?" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -16660,7 +16667,7 @@ msgstr "" "Однако, хотя такое поведение является естественным следствием дизайна " "формата, полагаться на него, как правило, не рекомендуется." -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -16679,7 +16686,7 @@ msgstr "" "безопасности, или полная интеграция со стандартным механизмом сборки для C-" "расширений путем публикации заголовочных файлов в соответствующем месте)." -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -16712,7 +16719,7 @@ msgstr "" "взаимодействие с внешними компонентами все равно может потребовать наличия " "реального файла на диске." -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -16726,7 +16733,7 @@ msgstr "" "имейте в виду, что многие проекты потребуют воспроизвести сбой с полностью " "установленным пакетом, прежде чем принять его за настоящую ошибку." -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -16746,11 +16753,11 @@ msgstr "" msgid "History" msgstr "История" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "Февраль 2013 г: Эта спецификация была одобрена через :pep:`427`." -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." @@ -16759,7 +16766,7 @@ msgstr "" "пересмотрены, чтобы привести их в соответствие с тем, что на самом деле " "делают популярные инструменты." -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -16767,7 +16774,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 #, fuzzy #| msgid "" @@ -16781,10 +16788,16 @@ msgstr "" "через :pep:`625`." #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "Приложение" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "Пример реализации urlsafe-base64-nopad::" diff --git a/locales/sai/LC_MESSAGES/messages.po b/locales/sai/LC_MESSAGES/messages.po index 15be53889..03f27184d 100644 --- a/locales/sai/LC_MESSAGES/messages.po +++ b/locales/sai/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/si/LC_MESSAGES/messages.po b/locales/si/LC_MESSAGES/messages.po index 379e92e1a..49fd9e2a5 100644 --- a/locales/si/LC_MESSAGES/messages.po +++ b/locales/si/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2022-06-11 08:19+0000\n" "Last-Translator: Kushan Gunasekera \n" "Language-Team: Sinhala ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12347,7 +12349,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12355,64 +12357,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12420,28 +12422,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12450,22 +12452,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12473,11 +12475,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12486,29 +12488,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12518,7 +12520,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12526,7 +12528,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12534,17 +12536,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12552,39 +12554,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12594,11 +12596,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12607,38 +12609,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12646,7 +12648,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12654,18 +12656,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12674,7 +12676,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12685,7 +12687,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12703,7 +12705,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12712,7 +12714,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12732,17 +12734,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12750,7 +12752,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12758,10 +12760,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index 94bfd5c2d..899a00868 100644 --- a/locales/sk/LC_MESSAGES/messages.po +++ b/locales/sk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-11-02 00:54+0000\n" "Last-Translator: Milan Šalka \n" "Language-Team: Slovak ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12505,7 +12507,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12513,64 +12515,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12578,28 +12580,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12608,22 +12610,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12631,11 +12633,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12644,29 +12646,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12676,7 +12678,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12684,7 +12686,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12692,17 +12694,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12710,39 +12712,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12752,11 +12754,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12765,38 +12767,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12804,7 +12806,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12812,18 +12814,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12832,7 +12834,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12843,7 +12845,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12861,7 +12863,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12870,7 +12872,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12890,17 +12892,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12908,7 +12910,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12916,10 +12918,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/ta/LC_MESSAGES/messages.po b/locales/ta/LC_MESSAGES/messages.po index e36ef606d..3a0c63d13 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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12314,28 +12314,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12343,7 +12345,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12351,64 +12353,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12416,28 +12418,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12446,22 +12448,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12469,11 +12471,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12482,29 +12484,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12514,7 +12516,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12522,7 +12524,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12530,17 +12532,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12548,39 +12550,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12590,11 +12592,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12603,38 +12605,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12642,7 +12644,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12650,18 +12652,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12670,7 +12672,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12681,7 +12683,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12699,7 +12701,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12708,7 +12710,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12728,17 +12730,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12746,7 +12748,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12754,10 +12756,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/tr/LC_MESSAGES/messages.po b/locales/tr/LC_MESSAGES/messages.po index 2b4863798..a964cd854 100644 --- a/locales/tr/LC_MESSAGES/messages.po +++ b/locales/tr/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-10-16 20:19+0000\n" "Last-Translator: Emr \n" "Language-Team: Turkish ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12346,7 +12348,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12354,64 +12356,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12419,28 +12421,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12449,22 +12451,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12472,11 +12474,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12485,29 +12487,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12517,7 +12519,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12525,7 +12527,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12533,17 +12535,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12551,39 +12553,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12593,11 +12595,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12606,38 +12608,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12645,7 +12647,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12653,18 +12655,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12673,7 +12675,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12684,7 +12686,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12702,7 +12704,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12711,7 +12713,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12731,17 +12733,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12749,7 +12751,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12757,10 +12759,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/uk/LC_MESSAGES/messages.po b/locales/uk/LC_MESSAGES/messages.po index ae70b8db0..3264cf510 100644 --- a/locales/uk/LC_MESSAGES/messages.po +++ b/locales/uk/LC_MESSAGES/messages.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-03-01 20:00+0000\n" "Last-Translator: Sviatoslav Sydorenko \n" "Language-Team: Ukrainian ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12877,7 +12879,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12885,64 +12887,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12950,28 +12952,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12980,22 +12982,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -13003,11 +13005,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -13016,29 +13018,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -13048,7 +13050,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -13056,7 +13058,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -13064,17 +13066,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -13082,15 +13084,15 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 #, fuzzy msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" @@ -13098,26 +13100,26 @@ msgid "" msgstr "" "https://self-issued.info/docs/draft-jones-jose-jws-json-serialization.html" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 #, fuzzy msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "https://self-issued.info/docs/draft-jones-jose-json-private-key.html" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "ЧаПи" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -13127,11 +13129,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -13140,38 +13142,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -13179,7 +13181,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -13187,18 +13189,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -13207,7 +13209,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -13218,7 +13220,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -13236,7 +13238,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -13245,7 +13247,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -13265,17 +13267,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -13283,7 +13285,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -13291,10 +13293,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "Додаток" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/vi/LC_MESSAGES/messages.po b/locales/vi/LC_MESSAGES/messages.po index c59dbf68d..ab7024de5 100644 --- a/locales/vi/LC_MESSAGES/messages.po +++ b/locales/vi/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2024-07-25 13:10+0000\n" "Last-Translator: Lenny Tran \n" "Language-Team: Vietnamese ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12371,7 +12373,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12379,64 +12381,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12444,28 +12446,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12474,22 +12476,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12497,11 +12499,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12510,29 +12512,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12542,7 +12544,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12550,7 +12552,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12558,17 +12560,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12576,39 +12578,39 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12618,11 +12620,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12631,38 +12633,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12670,7 +12672,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12678,18 +12680,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12698,7 +12700,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12709,7 +12711,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12727,7 +12729,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12736,7 +12738,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12756,17 +12758,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12774,7 +12776,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12782,10 +12784,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/zh_Hans/LC_MESSAGES/messages.po b/locales/zh_Hans/LC_MESSAGES/messages.po index ad2d8a330..bd6c42864 100644 --- a/locales/zh_Hans/LC_MESSAGES/messages.po +++ b/locales/zh_Hans/LC_MESSAGES/messages.po @@ -32,10 +32,10 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-16 14:00+0000\n" -"Last-Translator: 大王叫我来巡山 " -"\n" +"Last-Translator: 大王叫我来巡山 \n" "Language-Team: Chinese (Simplified Han script) \n" "Language: zh_Hans\n" @@ -13263,28 +13263,30 @@ msgstr "" #: ../source/specifications/binary-distribution-format.rst:177 msgid "" -"The contents of a wheel file, where {distribution} is replaced with the name " -"of the package, e.g. ``beaglevote`` and {version} is replaced with its " -"version, e.g. ``1.0.0``, consist of:" +"The contents of a wheel file, where {distribution} is replaced with the :ref:" +"`normalized name ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -13292,7 +13294,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -13300,64 +13302,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "Wheel 不包含 setup.py 或 setup.cfg。" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -13365,28 +13367,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "目录 .dist-info" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -13395,22 +13397,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -13418,13 +13420,13 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 #, fuzzy #| msgid "The .dist-info directory" msgid "The :file:`.dist-info/licenses/` directory" msgstr "目录 .dist-info" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -13433,29 +13435,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr ".data 目录" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -13465,7 +13467,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -13473,7 +13475,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -13481,17 +13483,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -13499,15 +13501,15 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "见" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" @@ -13515,26 +13517,26 @@ msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -13544,11 +13546,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -13557,38 +13559,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -13596,7 +13598,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -13604,18 +13606,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -13624,7 +13626,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -13635,7 +13637,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -13653,7 +13655,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -13662,7 +13664,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -13682,17 +13684,17 @@ msgstr "" msgid "History" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -13700,7 +13702,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -13708,10 +13710,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr "" diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po index 119ac825f..45aa4ead3 100644 --- a/locales/zh_Hant/LC_MESSAGES/messages.po +++ b/locales/zh_Hant/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: 2025-01-15 04:02+0000\n" +"POT-Creation-Date: 2025-01-21 12:28+0000\n" "PO-Revision-Date: 2025-01-10 00:29+0000\n" "Last-Translator: nonepork <59335048+nonepork@users.noreply.github.com>\n" "Language-Team: Chinese (Traditional Han script) ` of the package, e.g. ``beaglevote`` " +"and {version} is replaced with its :ref:`normalized version `, e.g. ``1.0.0``, (with dash/``-`` characters " +"replaced with underscore/``_`` characters in both fields) consist of:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:181 +#: ../source/specifications/binary-distribution-format.rst:184 msgid "" "``/``, the root of the archive, contains all files to be installed in " "``purelib`` or ``platlib`` as specified in ``WHEEL``. ``purelib`` and " "``platlib`` are usually both ``site-packages``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:184 +#: ../source/specifications/binary-distribution-format.rst:187 msgid "``{distribution}-{version}.dist-info/`` contains metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:185 +#: ../source/specifications/binary-distribution-format.rst:188 msgid "" ":file:`{distribution}-{version}.dist-info/licenses/` contains license files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:186 +#: ../source/specifications/binary-distribution-format.rst:189 msgid "" "``{distribution}-{version}.data/`` contains one subdirectory for each non-" "empty install scheme key not already covered, where the subdirectory name is " @@ -12451,7 +12453,7 @@ msgid "" "``headers``, ``purelib``, ``platlib``)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:190 +#: ../source/specifications/binary-distribution-format.rst:193 msgid "" "Python scripts must appear in ``scripts`` and begin with exactly ``b'#!" "python'`` in order to enjoy script wrapper generation and ``#!python`` " @@ -12459,64 +12461,64 @@ msgid "" "``scripts`` directory may only contain regular files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:194 +#: ../source/specifications/binary-distribution-format.rst:197 msgid "" "``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1 or " "greater format metadata." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:196 +#: ../source/specifications/binary-distribution-format.rst:199 msgid "" "``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive " "itself in the same basic key: value format::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:206 +#: ../source/specifications/binary-distribution-format.rst:209 msgid "``Wheel-Version`` is the version number of the Wheel specification." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:207 +#: ../source/specifications/binary-distribution-format.rst:210 msgid "" "``Generator`` is the name and optionally the version of the software that " "produced the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:209 +#: ../source/specifications/binary-distribution-format.rst:212 msgid "" "``Root-Is-Purelib`` is true if the top level directory of the archive should " "be installed into purelib; otherwise the root should be installed into " "platlib." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:212 +#: ../source/specifications/binary-distribution-format.rst:215 msgid "" "``Tag`` is the wheel's expanded compatibility tags; in the example the " "filename would contain ``py2.py3-none-any``." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:214 +#: ../source/specifications/binary-distribution-format.rst:217 msgid "" "``Build`` is the build number and is omitted if there is no build number." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:215 +#: ../source/specifications/binary-distribution-format.rst:218 msgid "" "A wheel installer should warn if Wheel-Version is greater than the version " "it supports, and must fail if Wheel-Version has a greater major version than " "the version it supports." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:218 +#: ../source/specifications/binary-distribution-format.rst:221 msgid "" "Wheel, being an installation format that is intended to work across multiple " "versions of Python, does not generally include .pyc files." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:220 +#: ../source/specifications/binary-distribution-format.rst:223 msgid "Wheel does not contain setup.py or setup.cfg." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:222 +#: ../source/specifications/binary-distribution-format.rst:225 msgid "" "This version of the wheel specification is based on the distutils install " "schemes and does not define how to install files to other locations. The " @@ -12524,28 +12526,28 @@ msgid "" "wininst and egg binary formats." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:229 +#: ../source/specifications/binary-distribution-format.rst:232 #: ../source/specifications/recording-installed-packages.rst:23 msgid "The .dist-info directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:231 +#: ../source/specifications/binary-distribution-format.rst:234 msgid "" "Wheel .dist-info directories include at a minimum METADATA, WHEEL, and " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:233 +#: ../source/specifications/binary-distribution-format.rst:236 msgid "" "METADATA is the package metadata, the same format as PKG-INFO as found at " "the root of sdists." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:235 +#: ../source/specifications/binary-distribution-format.rst:238 msgid "WHEEL is the wheel metadata specific to a build of the package." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:236 +#: ../source/specifications/binary-distribution-format.rst:239 msgid "" "RECORD is a list of (almost) all the files in the wheel and their secure " "hashes. Unlike PEP 376, every file except RECORD, which cannot contain a " @@ -12554,22 +12556,22 @@ msgid "" "rely on the strong hashes in RECORD to validate the integrity of the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:242 +#: ../source/specifications/binary-distribution-format.rst:245 msgid "PEP 376's INSTALLER and REQUESTED are not included in the archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:243 +#: ../source/specifications/binary-distribution-format.rst:246 msgid "" "RECORD.jws is used for digital signatures. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:245 +#: ../source/specifications/binary-distribution-format.rst:248 msgid "" "RECORD.p7s is allowed as a courtesy to anyone who would prefer to use S/MIME " "signatures to secure their wheel files. It is not mentioned in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:248 +#: ../source/specifications/binary-distribution-format.rst:251 msgid "" "During extraction, wheel installers verify all the hashes in RECORD against " "the file contents. Apart from RECORD and its signatures, installation will " @@ -12577,11 +12579,11 @@ msgid "" "in RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:255 +#: ../source/specifications/binary-distribution-format.rst:258 msgid "The :file:`.dist-info/licenses/` directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:257 +#: ../source/specifications/binary-distribution-format.rst:260 msgid "" "If the metadata version is 2.4 or greater and one or more ``License-File`` " "fields is specified, the :file:`.dist-info/` directory MUST contain a :file:" @@ -12590,29 +12592,29 @@ msgid "" "paths relative to the :file:`licenses/` directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:265 +#: ../source/specifications/binary-distribution-format.rst:268 msgid "The .data directory" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:267 +#: ../source/specifications/binary-distribution-format.rst:270 msgid "" "Any file that is not normally installed inside site-packages goes into the ." "data directory, named as the .dist-info directory but with the .data/ " "extension::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:275 +#: ../source/specifications/binary-distribution-format.rst:278 msgid "" "The .data directory contains subdirectories with the scripts, headers, " "documentation and so forth from the distribution. During installation the " "contents of these subdirectories are moved onto their destination paths." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:281 +#: ../source/specifications/binary-distribution-format.rst:284 msgid "Signed wheel files" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:283 +#: ../source/specifications/binary-distribution-format.rst:286 msgid "" "Wheel files include an extended RECORD that enables digital signatures. PEP " "376's RECORD is altered to include a secure hash " @@ -12622,7 +12624,7 @@ msgid "" "files, but not RECORD which cannot contain its own hash. For example::" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:294 +#: ../source/specifications/binary-distribution-format.rst:297 msgid "" "The signature file(s) RECORD.jws and RECORD.p7s are not mentioned in RECORD " "at all since they can only be added after RECORD is generated. Every other " @@ -12630,7 +12632,7 @@ msgid "" "will fail." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:299 +#: ../source/specifications/binary-distribution-format.rst:302 msgid "" "If JSON web signatures are used, one or more JSON Web Signature JSON " "Serialization (JWS-JS) signatures is stored in a file RECORD.jws adjacent to " @@ -12638,17 +12640,17 @@ msgid "" "as the signature's JSON payload:" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:308 +#: ../source/specifications/binary-distribution-format.rst:311 msgid "(The hash value is the same format used in RECORD.)" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:310 +#: ../source/specifications/binary-distribution-format.rst:313 msgid "" "If RECORD.p7s is used, it must contain a detached S/MIME format signature of " "RECORD." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:313 +#: ../source/specifications/binary-distribution-format.rst:316 msgid "" "A wheel installer is not required to understand digital signatures but MUST " "verify the hashes in RECORD against the extracted file contents. When the " @@ -12656,41 +12658,41 @@ msgid "" "only needs to establish that RECORD matches the signature." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:318 +#: ../source/specifications/binary-distribution-format.rst:321 msgid "See" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:320 +#: ../source/specifications/binary-distribution-format.rst:323 msgid "https://datatracker.ietf.org/doc/html/rfc7515" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:321 +#: ../source/specifications/binary-distribution-format.rst:324 #, fuzzy msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-json-web-signature-json-" "serialization-01" msgstr "http://self-issued.info/docs/draft-jones-jose-json-private-key.html" -#: ../source/specifications/binary-distribution-format.rst:322 +#: ../source/specifications/binary-distribution-format.rst:325 msgid "https://datatracker.ietf.org/doc/html/rfc7517" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:323 +#: ../source/specifications/binary-distribution-format.rst:326 #, fuzzy msgid "" "https://datatracker.ietf.org/doc/html/draft-jones-jose-json-private-key-01" msgstr "http://self-issued.info/docs/draft-jones-jose-json-private-key.html" -#: ../source/specifications/binary-distribution-format.rst:327 +#: ../source/specifications/binary-distribution-format.rst:330 #: ../source/specifications/platform-compatibility-tags.rst:268 msgid "FAQ" msgstr "常見問題" -#: ../source/specifications/binary-distribution-format.rst:331 +#: ../source/specifications/binary-distribution-format.rst:334 msgid "Wheel defines a .data directory. Should I put all my data there?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:333 +#: ../source/specifications/binary-distribution-format.rst:336 msgid "" "This specification does not have an opinion on how you should organize your " "code. The .data directory is just a place for any files that are not " @@ -12700,11 +12702,11 @@ msgid "" "directory." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:342 +#: ../source/specifications/binary-distribution-format.rst:345 msgid "Why does wheel include attached signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:344 +#: ../source/specifications/binary-distribution-format.rst:347 msgid "" "Attached signatures are more convenient than detached signatures because " "they travel with the archive. Since only the individual files are signed, " @@ -12713,38 +12715,38 @@ msgid "" "archive." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:352 +#: ../source/specifications/binary-distribution-format.rst:355 msgid "Why does wheel allow JWS signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:354 +#: ../source/specifications/binary-distribution-format.rst:357 msgid "" "The JOSE specifications of which JWS is a part are designed to be easy to " "implement, a feature that is also one of wheel's primary design goals. JWS " "yields a useful, concise pure-Python implementation." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:360 +#: ../source/specifications/binary-distribution-format.rst:363 msgid "Why does wheel also allow S/MIME signatures?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:362 +#: ../source/specifications/binary-distribution-format.rst:365 msgid "" "S/MIME signatures are allowed for users who need or want to use existing " "public key infrastructure with wheel." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:365 +#: ../source/specifications/binary-distribution-format.rst:368 msgid "" "Signed packages are only a basic building block in a secure package update " "system. Wheel only provides the building block." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:370 +#: ../source/specifications/binary-distribution-format.rst:373 msgid "What's the deal with \"purelib\" vs. \"platlib\"?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:372 +#: ../source/specifications/binary-distribution-format.rst:375 msgid "" "Wheel preserves the \"purelib\" vs. \"platlib\" distinction, which is " "significant on some platforms. For example, Fedora installs pure Python " @@ -12752,7 +12754,7 @@ msgid "" "packages to '/usr/lib64/pythonX.Y/site-packages'." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:377 +#: ../source/specifications/binary-distribution-format.rst:380 msgid "" "A wheel with \"Root-Is-Purelib: false\" with all its files in ``{name}-" "{version}.data/purelib`` is equivalent to a wheel with \"Root-Is-Purelib: " @@ -12760,18 +12762,18 @@ msgid "" "both the \"purelib\" and \"platlib\" categories." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:382 +#: ../source/specifications/binary-distribution-format.rst:385 msgid "" "In practice a wheel should have only one of \"purelib\" or \"platlib\" " "depending on whether it is pure Python or not and those files should be at " "the root with the appropriate setting given for \"Root-is-purelib\"." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:390 +#: ../source/specifications/binary-distribution-format.rst:393 msgid "Is it possible to import Python code directly from a wheel file?" msgstr "" -#: ../source/specifications/binary-distribution-format.rst:392 +#: ../source/specifications/binary-distribution-format.rst:395 msgid "" "Technically, due to the combination of supporting installation via simple " "extraction and using an archive format that is compatible with " @@ -12780,7 +12782,7 @@ msgid "" "format design, actually relying on it is generally discouraged." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:398 +#: ../source/specifications/binary-distribution-format.rst:401 msgid "" "Firstly, wheel *is* designed primarily as a distribution format, so skipping " "the installation step also means deliberately avoiding any reliance on " @@ -12791,7 +12793,7 @@ msgid "" "extensions by publishing header files in the appropriate place)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:407 +#: ../source/specifications/binary-distribution-format.rst:410 msgid "" "Secondly, while some Python software is written to support running directly " "from a zip archive, it is still common for code to be written assuming it " @@ -12809,7 +12811,7 @@ msgid "" "components may still require the availability of an actual on-disk file." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:424 +#: ../source/specifications/binary-distribution-format.rst:427 msgid "" "Like metaclasses, monkeypatching and metapath importers, if you're not " "already sure you need to take advantage of this feature, you almost " @@ -12818,7 +12820,7 @@ msgid "" "package before accepting it as a genuine bug." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:432 +#: ../source/specifications/binary-distribution-format.rst:435 #: ../source/specifications/core-metadata.rst:922 #: ../source/specifications/dependency-groups.rst:248 #: ../source/specifications/dependency-specifiers.rst:487 @@ -12838,17 +12840,17 @@ msgstr "" msgid "History" msgstr "歷史" -#: ../source/specifications/binary-distribution-format.rst:434 +#: ../source/specifications/binary-distribution-format.rst:437 msgid "February 2013: This specification was approved through :pep:`427`." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:435 +#: ../source/specifications/binary-distribution-format.rst:438 msgid "" "February 2021: The rules on escaping in wheel filenames were revised, to " "bring them into line with what popular tools actually do." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:437 +#: ../source/specifications/binary-distribution-format.rst:440 msgid "" "December 2024: Clarified that the ``scripts`` folder should only contain " "regular files (the expected behaviour of consuming tools when encountering " @@ -12856,7 +12858,7 @@ msgid "" "may vary between tools)." msgstr "" -#: ../source/specifications/binary-distribution-format.rst:441 +#: ../source/specifications/binary-distribution-format.rst:444 #: ../source/specifications/recording-installed-packages.rst:278 msgid "" "December 2024: The :file:`.dist-info/licenses/` directory was specified " @@ -12864,10 +12866,16 @@ msgid "" msgstr "" #: ../source/specifications/binary-distribution-format.rst:446 +msgid "" +"January 2025: Clarified that name and version needs to be normalized for ``." +"dist-info`` and ``.data`` directories." +msgstr "" + +#: ../source/specifications/binary-distribution-format.rst:451 msgid "Appendix" msgstr "附錄" -#: ../source/specifications/binary-distribution-format.rst:448 +#: ../source/specifications/binary-distribution-format.rst:453 msgid "Example urlsafe-base64-nopad implementation::" msgstr ""