# Copyright (C) 2001-2020, Python Software Foundation

# This file is distributed under the same license as the Python package.

# Maintained by the python-doc-es workteam.

# docs-es@python.org / https://mail.python.org/mailman3/lists/docs-es.python.org/

# Check https://github.com/PyCampES/python-docs-es/blob/3.7/TRANSLATORS to get the list of volunteers

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.7\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2019-05-06 11:59-0400\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: python-doc-es (https://mail.python.org/mailman3/lists/docs-es.python.org)\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

#: ../Doc/extending/building.rst:7

msgid "Building C and C++ Extensions"

msgstr ""

#: ../Doc/extending/building.rst:9

msgid ""

"A C extension for CPython is a shared library (e.g. a ``.so`` file on Linux, "

"``.pyd`` on Windows), which exports an *initialization function*."

msgstr ""

#: ../Doc/extending/building.rst:12

msgid ""

"To be importable, the shared library must be available on :envvar:"

"`PYTHONPATH`, and must be named after the module name, with an appropriate "

"extension. When using distutils, the correct filename is generated "

"automatically."

msgstr ""

#: ../Doc/extending/building.rst:16

msgid "The initialization function has the signature:"

msgstr ""

#: ../Doc/extending/building.rst:20

msgid ""

"It returns either a fully-initialized module, or a :c:type:`PyModuleDef` "

"instance. See :ref:`initializing-modules` for details."

msgstr ""

#: ../Doc/extending/building.rst:25

msgid ""

"For modules with ASCII-only names, the function must be named "

"``PyInit_<modulename>``, with ``<modulename>`` replaced by the name of the "

"module. When using :ref:`multi-phase-initialization`, non-ASCII module names "

"are allowed. In this case, the initialization function name is "

"``PyInitU_<modulename>``, with ``<modulename>`` encoded using Python's "

"*punycode* encoding with hyphens replaced by underscores. In Python::"

msgstr ""

#: ../Doc/extending/building.rst:39

msgid ""

"It is possible to export multiple modules from a single shared library by "

"defining multiple initialization functions. However, importing them requires "

"using symbolic links or a custom importer, because by default only the "

"function corresponding to the filename is found. See the *\"Multiple modules "

"in one library\"* section in :pep:`489` for details."

msgstr ""

#: ../Doc/extending/building.rst:49

msgid "Building C and C++ Extensions with distutils"

msgstr ""

#: ../Doc/extending/building.rst:53

msgid ""

"Extension modules can be built using distutils, which is included in "

"Python. Since distutils also supports creation of binary packages, users "

"don't necessarily need a compiler and distutils to install the extension."

msgstr ""

#: ../Doc/extending/building.rst:57

msgid ""

"A distutils package contains a driver script, :file:`setup.py`. This is a "

"plain Python file, which, in the most simple case, could look like this:"

msgstr ""

#: ../Doc/extending/building.rst:73

msgid "With this :file:`setup.py`, and a file :file:`demo.c`, running ::"

msgstr ""

#: ../Doc/extending/building.rst:77

msgid ""

"will compile :file:`demo.c`, and produce an extension module named ``demo`` "

"in the :file:`build` directory. Depending on the system, the module file "

"will end up in a subdirectory :file:`build/lib.system`, and may have a name "

"like :file:`demo.so` or :file:`demo.pyd`."

msgstr ""

#: ../Doc/extending/building.rst:82

msgid ""

"In the :file:`setup.py`, all execution is performed by calling the ``setup`` "

"function. This takes a variable number of keyword arguments, of which the "

"example above uses only a subset. Specifically, the example specifies meta-"

"information to build packages, and it specifies the contents of the "

"package. Normally, a package will contain additional modules, like Python "

"source modules, documentation, subpackages, etc. Please refer to the "

"distutils documentation in :ref:`distutils-index` to learn more about the "

"features of distutils; this section explains building extension modules only."

msgstr ""

#: ../Doc/extending/building.rst:91

msgid ""

"It is common to pre-compute arguments to :func:`setup`, to better structure "

"the driver script. In the example above, the ``ext_modules`` argument to :"

"func:`~distutils.core.setup` is a list of extension modules, each of which "

"is an instance of the :class:`~distutils.extension.Extension`. In the "

"example, the instance defines an extension named ``demo`` which is build by "

"compiling a single source file, :file:`demo.c`."

msgstr ""

#: ../Doc/extending/building.rst:99

msgid ""

"In many cases, building an extension is more complex, since additional "

"preprocessor defines and libraries may be needed. This is demonstrated in "

"the example below."

msgstr ""

#: ../Doc/extending/building.rst:127

msgid ""

"In this example, :func:`~distutils.core.setup` is called with additional "

"meta-information, which is recommended when distribution packages have to be "

"built. For the extension itself, it specifies preprocessor defines, include "

"directories, library directories, and libraries. Depending on the compiler, "

"distutils passes this information in different ways to the compiler. For "

"example, on Unix, this may result in the compilation commands ::"

msgstr ""

#: ../Doc/extending/building.rst:139

msgid ""

"These lines are for demonstration purposes only; distutils users should "

"trust that distutils gets the invocations right."

msgstr ""

#: ../Doc/extending/building.rst:146

msgid "Distributing your extension modules"

msgstr ""

#: ../Doc/extending/building.rst:148

msgid ""

"When an extension has been successfully build, there are three ways to use "

"it."

msgstr ""

#: ../Doc/extending/building.rst:150

msgid ""

"End-users will typically want to install the module, they do so by running ::"

msgstr ""

#: ../Doc/extending/building.rst:154

msgid ""

"Module maintainers should produce source packages; to do so, they run ::"

msgstr ""

#: ../Doc/extending/building.rst:158

msgid ""

"In some cases, additional files need to be included in a source "

"distribution; this is done through a :file:`MANIFEST.in` file; see :ref:"

"`manifest` for details."

msgstr ""

#: ../Doc/extending/building.rst:161

msgid ""

"If the source distribution has been build successfully, maintainers can also "

"create binary distributions. Depending on the platform, one of the following "

"commands can be used to do so. ::"

msgstr ""