Skip to content

Commit 82dc936

Browse files
committed
update python-newest.extending--building/id.po with latest contents from transifex
1 parent 24f7386 commit 82dc936

File tree

1 file changed

+24
-111
lines changed
  • python-newest.extending--building

1 file changed

+24
-111
lines changed
Lines changed: 24 additions & 111 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# SOME DESCRIPTIVE TITLE.
2-
# Copyright (C) 2001-2019, Python Software Foundation
2+
# Copyright (C) 2001 Python Software Foundation
33
# This file is distributed under the same license as the Python package.
44
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55
#
66
#, fuzzy
77
msgid ""
88
msgstr ""
9-
"Project-Id-Version: Python 3.8\n"
9+
"Project-Id-Version: Python 3.14\n"
1010
"Report-Msgid-Bugs-To: \n"
11-
"POT-Creation-Date: 2019-09-01 14:24+0000\n"
12-
"PO-Revision-Date: 2017-02-16 17:42+0000\n"
13-
"Language-Team: Indonesian (https://www.transifex.com/python-doc/teams/5390/id/)\n"
11+
"POT-Creation-Date: 2025-05-09 14:19+0000\n"
12+
"PO-Revision-Date: 2021-06-28 00:51+0000\n"
13+
"Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/id/)\n"
1414
"MIME-Version: 1.0\n"
1515
"Content-Type: text/plain; charset=UTF-8\n"
1616
"Content-Transfer-Encoding: 8bit\n"
@@ -31,7 +31,7 @@ msgstr ""
3131
msgid ""
3232
"To be importable, the shared library must be available on "
3333
":envvar:`PYTHONPATH`, and must be named after the module name, with an "
34-
"appropriate extension. When using distutils, the correct filename is "
34+
"appropriate extension. When using setuptools, the correct filename is "
3535
"generated automatically."
3636
msgstr ""
3737

@@ -41,7 +41,7 @@ msgstr ""
4141

4242
#: ../../extending/building.rst:20
4343
msgid ""
44-
"It returns either a fully-initialized module, or a :c:type:`PyModuleDef` "
44+
"It returns either a fully initialized module, or a :c:type:`PyModuleDef` "
4545
"instance. See :ref:`initializing-modules` for details."
4646
msgstr ""
4747

@@ -55,6 +55,16 @@ msgid ""
5555
"*punycode* encoding with hyphens replaced by underscores. In Python::"
5656
msgstr ""
5757

58+
#: ../../extending/building.rst:32
59+
msgid ""
60+
"def initfunc_name(name):\n"
61+
" try:\n"
62+
" suffix = b'_' + name.encode('ascii')\n"
63+
" except UnicodeEncodeError:\n"
64+
" suffix = b'U_' + name.encode('punycode').replace(b'-', b'_')\n"
65+
" return b'PyInit' + suffix"
66+
msgstr ""
67+
5868
#: ../../extending/building.rst:39
5969
msgid ""
6070
"It is possible to export multiple modules from a single shared library by "
@@ -64,111 +74,14 @@ msgid ""
6474
" in one library\"* section in :pep:`489` for details."
6575
msgstr ""
6676

67-
#: ../../extending/building.rst:49
68-
msgid "Building C and C++ Extensions with distutils"
69-
msgstr ""
70-
71-
#: ../../extending/building.rst:53
72-
msgid ""
73-
"Extension modules can be built using distutils, which is included in "
74-
"Python. Since distutils also supports creation of binary packages, users "
75-
"don't necessarily need a compiler and distutils to install the extension."
76-
msgstr ""
77-
78-
#: ../../extending/building.rst:57
79-
msgid ""
80-
"A distutils package contains a driver script, :file:`setup.py`. This is a "
81-
"plain Python file, which, in the most simple case, could look like this:"
82-
msgstr ""
83-
84-
#: ../../extending/building.rst:73
85-
msgid "With this :file:`setup.py`, and a file :file:`demo.c`, running ::"
86-
msgstr ""
87-
88-
#: ../../extending/building.rst:77
89-
msgid ""
90-
"will compile :file:`demo.c`, and produce an extension module named ``demo`` "
91-
"in the :file:`build` directory. Depending on the system, the module file "
92-
"will end up in a subdirectory :file:`build/lib.system`, and may have a name "
93-
"like :file:`demo.so` or :file:`demo.pyd`."
94-
msgstr ""
95-
96-
#: ../../extending/building.rst:82
97-
msgid ""
98-
"In the :file:`setup.py`, all execution is performed by calling the ``setup``"
99-
" function. This takes a variable number of keyword arguments, of which the "
100-
"example above uses only a subset. Specifically, the example specifies meta-"
101-
"information to build packages, and it specifies the contents of the package."
102-
" Normally, a package will contain additional modules, like Python source "
103-
"modules, documentation, subpackages, etc. Please refer to the distutils "
104-
"documentation in :ref:`distutils-index` to learn more about the features of "
105-
"distutils; this section explains building extension modules only."
106-
msgstr ""
107-
108-
#: ../../extending/building.rst:91
109-
msgid ""
110-
"It is common to pre-compute arguments to :func:`setup`, to better structure "
111-
"the driver script. In the example above, the ``ext_modules`` argument to "
112-
":func:`~distutils.core.setup` is a list of extension modules, each of which "
113-
"is an instance of the :class:`~distutils.extension.Extension`. In the "
114-
"example, the instance defines an extension named ``demo`` which is build by "
115-
"compiling a single source file, :file:`demo.c`."
116-
msgstr ""
117-
118-
#: ../../extending/building.rst:99
119-
msgid ""
120-
"In many cases, building an extension is more complex, since additional "
121-
"preprocessor defines and libraries may be needed. This is demonstrated in "
122-
"the example below."
123-
msgstr ""
124-
125-
#: ../../extending/building.rst:127
126-
msgid ""
127-
"In this example, :func:`~distutils.core.setup` is called with additional "
128-
"meta-information, which is recommended when distribution packages have to be"
129-
" built. For the extension itself, it specifies preprocessor defines, include"
130-
" directories, library directories, and libraries. Depending on the compiler,"
131-
" distutils passes this information in different ways to the compiler. For "
132-
"example, on Unix, this may result in the compilation commands ::"
133-
msgstr ""
134-
135-
#: ../../extending/building.rst:139
136-
msgid ""
137-
"These lines are for demonstration purposes only; distutils users should "
138-
"trust that distutils gets the invocations right."
139-
msgstr ""
140-
141-
#: ../../extending/building.rst:146
142-
msgid "Distributing your extension modules"
143-
msgstr ""
144-
145-
#: ../../extending/building.rst:148
146-
msgid ""
147-
"When an extension has been successfully built, there are three ways to use "
148-
"it."
149-
msgstr ""
150-
151-
#: ../../extending/building.rst:150
152-
msgid ""
153-
"End-users will typically want to install the module, they do so by running "
154-
"::"
155-
msgstr ""
156-
157-
#: ../../extending/building.rst:154
158-
msgid ""
159-
"Module maintainers should produce source packages; to do so, they run ::"
160-
msgstr ""
161-
162-
#: ../../extending/building.rst:158
163-
msgid ""
164-
"In some cases, additional files need to be included in a source "
165-
"distribution; this is done through a :file:`MANIFEST.in` file; see "
166-
":ref:`manifest` for details."
77+
#: ../../extending/building.rst:52
78+
msgid "Building C and C++ Extensions with setuptools"
16779
msgstr ""
16880

169-
#: ../../extending/building.rst:161
81+
#: ../../extending/building.rst:54
17082
msgid ""
171-
"If the source distribution has been built successfully, maintainers can also"
172-
" create binary distributions. Depending on the platform, one of the "
173-
"following commands can be used to do so. ::"
83+
"Python 3.12 and newer no longer come with distutils. Please refer to the "
84+
"``setuptools`` documentation at "
85+
"https://setuptools.readthedocs.io/en/latest/setuptools.html to learn more "
86+
"about how build and distribute C/C++ extensions with setuptools."
17487
msgstr ""

0 commit comments

Comments
 (0)