34
34
35
35
# "Cheng R.Zhu" <
[email protected] >, 2025.
36
36
# inworless <
[email protected] >, 2025.
37
+
37
38
msgid ""
38
39
msgstr ""
39
40
"Project-Id-Version: Python Packaging User Guide\n"
40
41
"Report-Msgid-Bugs-To: \n"
41
42
"POT-Creation-Date: 2025-06-19 01:36+0000\n"
42
- "PO-Revision-Date: 2025-07-18 07:02 +0000\n"
43
- "Last-Translator: inworless <20262029@aliyun .com>\n"
43
+ "PO-Revision-Date: 2025-07-19 06:36 +0000\n"
44
+ "Last-Translator: del1 <3933676724@qq .com>\n"
44
45
"Language-Team: Chinese (Simplified Han script) <https://hosted.weblate.org/"
45
46
"projects/pypa/packaging-python-org/zh_Hans/>\n"
46
47
"Language: zh_Hans\n"
@@ -1108,6 +1109,9 @@ msgid ""
1108
1109
"commit tag information, potentially resulting in incorrect version details "
1109
1110
"in the resulting builds."
1110
1111
msgstr ""
1112
+ "明确发布存档文件可以确保在创建源归档时解决对版本控制系统元数据的任何依赖。例"
1113
+ "如,自动生成的Git存档会省略所有提交标签信息,可能会导致生成的构建中版本详细信"
1114
+ "息不正确。"
1111
1115
1112
1116
#: ../source/discussions/downstream-packaging.rst:99
1113
1117
#: ../source/discussions/downstream-packaging.rst:179
@@ -1125,8 +1129,12 @@ msgid ""
1125
1129
"documentation, and any other files that may be useful to end users, such as "
1126
1130
"shell completions, editor support files, and so on."
1127
1131
msgstr ""
1132
+ "理想情况下,**在PyPI上发布的源分发应包括来自软件包Git存储库**的所有文件,这些"
1133
+ "文件是构建软件包本身、运行其测试套件、构建和安装其文档以及可能对最终用户有用"
1134
+ "的任何其他文件所必需的,如外壳完成、编辑器支持文件等。"
1128
1135
1129
1136
#: ../source/discussions/downstream-packaging.rst:107
1137
+ #, fuzzy
1130
1138
msgid ""
1131
1139
"This point applies only to the files belonging to the package itself. The "
1132
1140
"downstream packaging process, much like Python package managers, will "
@@ -1136,6 +1144,10 @@ msgid ""
1136
1144
"files) should also be included, to help downstreams determine the needed "
1137
1145
"dependencies, and check for changes in them."
1138
1146
msgstr ""
1147
+ "这一点仅适用于属于软件包本身的文件。下游打包过程与Python软件包管理器非常类似"
1148
+ ",将配置您的软件包及其构建脚本所需的必要的Python依赖项、系统工具和外部库。然"
1149
+ "而,还应包括列出这些依赖项的文件(例如,“要求*.txt”文件),以帮助下游确定所需"
1150
+ "的依赖项,并检查其中是否有变化。"
1139
1151
1140
1152
#: ../source/discussions/downstream-packaging.rst:115
1141
1153
msgid ""
@@ -1149,6 +1161,11 @@ msgid ""
1149
1161
"Alternatively, large files, such as test data, can be split into separate "
1150
1162
"archives."
1151
1163
msgstr ""
1164
+ "一些项目对使用PyPI源分发的Python软件包管理器有关。他们不想用这些工具不使用的"
1165
+ "文件来增加它们的大小,或者他们根本不想发布源分发,因为它们允许从源代码构建特"
1166
+ "定项目的问题或完全无功能的后退。在这些情况下,一个好的折衷方案可能是发布一个"
1167
+ "单独的源代码归档,以便在其他地方下游使用,例如将其附加到GitHub版本中。或者,"
1168
+ "大型文件,如测试数据,可以拆分成单独的档案。"
1152
1169
1153
1170
#: ../source/discussions/downstream-packaging.rst:124
1154
1171
msgid ""
@@ -1160,6 +1177,10 @@ msgid ""
1160
1177
"was taken by the cryptography_ project, with the large test vectors being "
1161
1178
"split to cryptography-vectors_ package."
1162
1179
msgstr ""
1180
+ "另一方面,一些项目(例如NumPy_)决定在其已安装的软件包中包含测试。这具有允许"
1181
+ "用户在安装后运行测试的额外优势,例如在升级依赖项后检查回归。另一种方法是将测"
1182
+ "试或测试数据分割成一个单独的Python软件包。加密_项目采取了这种方法,将大型测试"
1183
+ "向量拆分为加密矢量_包。"
1163
1184
1164
1185
#: ../source/discussions/downstream-packaging.rst:132
1165
1186
msgid ""
@@ -1169,6 +1190,9 @@ msgid ""
1169
1190
"source distribution actually works, and that it won't accidentally install "
1170
1191
"fewer files than the official wheels."
1171
1192
msgstr ""
1193
+ "在发布流程中使用源分发是个不错的做法。例如,:ref:`build` "
1194
+ "工具正是这样操作的——它首先构建源分发,然后用它来构建 wheel "
1195
+ "包。这能确保源分发实际可用,同时避免意外遗漏官方 wheel 包中的文件。"
1172
1196
1173
1197
#: ../source/discussions/downstream-packaging.rst:138
1174
1198
msgid ""
0 commit comments