11# SOME DESCRIPTIVE TITLE.
2- # Copyright (C) 2001-2023, 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# Translators:
7- # Transifex Bot <>, 2023
7+ # Blessing Oluronbi, 2026
88#
99#, fuzzy
1010msgid ""
1111msgstr ""
12- "Project-Id-Version : Python 3.11 \n "
12+ "Project-Id-Version : Python 3.15 \n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2023 -05-19 14:13 +0000\n
15- "PO-Revision-Date : 2021-06-28 00:51 +0000\n
16- "Last-Translator : Transifex Bot <>, 2023 \n
14+ "POT-Creation-Date : 2026 -05-13 16:14 +0000\n
15+ "PO-Revision-Date : 2025-09-16 00:00 +0000\n
16+ "Last-Translator : Blessing Oluronbi, 2026 \n
1717"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
1818"MIME-Version : 1.0\n "
1919"Content-Type : text/plain; charset=UTF-8\n "
@@ -27,130 +27,29 @@ msgid "Building C and C++ Extensions"
2727msgstr ""
2828
2929msgid ""
30- "A C extension for CPython is a shared library (e.g. a ``.so`` file on Linux, "
31- "``.pyd`` on Windows), which exports an *initialization function*."
30+ "A C extension for CPython is a shared library (for example, a ``.so`` file "
31+ "on Linux, ``.pyd`` on Windows), which exports an *initialization function*."
3232msgstr ""
3333
34- msgid ""
35- "To be importable, the shared library must be available on :envvar:"
36- "`PYTHONPATH`, and must be named after the module name, with an appropriate "
37- "extension. When using distutils, the correct filename is generated "
38- "automatically."
39- msgstr ""
40-
41- msgid "The initialization function has the signature:"
42- msgstr ""
43-
44- msgid ""
45- "It returns either a fully initialized module, or a :c:type:`PyModuleDef` "
46- "instance. See :ref:`initializing-modules` for details."
47- msgstr ""
48-
49- msgid ""
50- "For modules with ASCII-only names, the function must be named "
51- "``PyInit_<modulename>``, with ``<modulename>`` replaced by the name of the "
52- "module. When using :ref:`multi-phase-initialization`, non-ASCII module names "
53- "are allowed. In this case, the initialization function name is "
54- "``PyInitU_<modulename>``, with ``<modulename>`` encoded using Python's "
55- "*punycode* encoding with hyphens replaced by underscores. In Python::"
56- msgstr ""
57-
58- msgid ""
59- "It is possible to export multiple modules from a single shared library by "
60- "defining multiple initialization functions. However, importing them requires "
61- "using symbolic links or a custom importer, because by default only the "
62- "function corresponding to the filename is found. See the *\" Multiple modules "
63- "in one library\" * section in :pep:`489` for details."
64- msgstr ""
65-
66- msgid "Building C and C++ Extensions with distutils"
67- msgstr ""
68-
69- msgid ""
70- "Extension modules can be built using distutils, which is included in "
71- "Python. Since distutils also supports creation of binary packages, users "
72- "don't necessarily need a compiler and distutils to install the extension."
73- msgstr ""
74-
75- msgid ""
76- "A distutils package contains a driver script, :file:`setup.py`. This is a "
77- "plain Python file, which, in the most simple case, could look like this:"
78- msgstr ""
79-
80- msgid "With this :file:`setup.py`, and a file :file:`demo.c`, running ::"
81- msgstr ""
82-
83- msgid ""
84- "will compile :file:`demo.c`, and produce an extension module named ``demo`` "
85- "in the :file:`build` directory. Depending on the system, the module file "
86- "will end up in a subdirectory :file:`build/lib.system`, and may have a name "
87- "like :file:`demo.so` or :file:`demo.pyd`."
34+ msgid "See :ref:`extension-modules` for details."
8835msgstr ""
8936
90- msgid ""
91- "In the :file:`setup.py`, all execution is performed by calling the ``setup`` "
92- "function. This takes a variable number of keyword arguments, of which the "
93- "example above uses only a subset. Specifically, the example specifies meta-"
94- "information to build packages, and it specifies the contents of the "
95- "package. Normally, a package will contain additional modules, like Python "
96- "source modules, documentation, subpackages, etc. Please refer to the "
97- "distutils documentation in :ref:`distutils-index` to learn more about the "
98- "features of distutils; this section explains building extension modules only."
99- msgstr ""
100-
101- msgid ""
102- "It is common to pre-compute arguments to :func:`setup`, to better structure "
103- "the driver script. In the example above, the ``ext_modules`` argument to :"
104- "func:`~distutils.core.setup` is a list of extension modules, each of which "
105- "is an instance of the :class:`~distutils.extension.Extension`. In the "
106- "example, the instance defines an extension named ``demo`` which is build by "
107- "compiling a single source file, :file:`demo.c`."
108- msgstr ""
109-
110- msgid ""
111- "In many cases, building an extension is more complex, since additional "
112- "preprocessor defines and libraries may be needed. This is demonstrated in "
113- "the example below."
114- msgstr ""
115-
116- msgid ""
117- "In this example, :func:`~distutils.core.setup` is called with additional "
118- "meta-information, which is recommended when distribution packages have to be "
119- "built. For the extension itself, it specifies preprocessor defines, include "
120- "directories, library directories, and libraries. Depending on the compiler, "
121- "distutils passes this information in different ways to the compiler. For "
122- "example, on Unix, this may result in the compilation commands ::"
123- msgstr ""
124-
125- msgid ""
126- "These lines are for demonstration purposes only; distutils users should "
127- "trust that distutils gets the invocations right."
128- msgstr ""
129-
130- msgid "Distributing your extension modules"
131- msgstr ""
132-
133- msgid ""
134- "When an extension has been successfully built, there are three ways to use "
135- "it."
136- msgstr ""
137-
138- msgid ""
139- "End-users will typically want to install the module, they do so by running ::"
140- msgstr ""
141-
142- msgid ""
143- "Module maintainers should produce source packages; to do so, they run ::"
37+ msgid "Building C and C++ Extensions with setuptools"
14438msgstr ""
14539
14640msgid ""
147- "In some cases, additional files need to be included in a source "
148- "distribution; this is done through a :file:`MANIFEST.in` file; see :ref:"
149- "`manifest` for details."
41+ "Building, packaging and distributing extension modules is best done with "
42+ "third-party tools, and is out of scope of this document. One suitable tool "
43+ "is Setuptools, whose documentation can be found at https://setuptools.pypa."
44+ "io/en/latest/setuptools.html."
15045msgstr ""
46+ "Kompilację, pakowanie i dystrybucję modułów rozszerzeń najlepiej wykonywać "
47+ "za pomocą narzędzi firm trzecich, co wykracza poza zakres niniejszego "
48+ "dokumentu. Jednym z odpowiednich narzędzi jest Setuptools, którego "
49+ "dokumentację można znaleźć pod adresem https://setuptools.pypa.io/en/latest/"
50+ "setuptools.html."
15151
15252msgid ""
153- "If the source distribution has been built successfully, maintainers can also "
154- "create binary distributions. Depending on the platform, one of the following "
155- "commands can be used to do so. ::"
53+ "The :mod:`distutils` module, which was included in the standard library "
54+ "until Python 3.12, is now maintained as part of Setuptools."
15655msgstr ""
0 commit comments