Traducido archivo c-api/perfmaps

Author: srmorita

c-api/perfmaps.po

@@ -10,15 +10,16 @@ msgstr ""
 "Project-Id-Version: Python en Español 3.12\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2024-11-21 16:38-0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language: es\n"
+"PO-Revision-Date: 2025-01-28 17:53-0300\n"
+"Last-Translator: srmorita <[email protected]>\n"
 "Language-Team: es <[email protected]>\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
 "Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.5\n"
 
 #: ../Doc/c-api/perfmaps.rst:6
 msgid "Support for Perf Maps"
@@ -28,12 +29,12 @@ msgstr ""
 msgid ""
 "On supported platforms (as of this writing, only Linux), the runtime can "
 "take advantage of *perf map files* to make Python functions visible to an "
-"external profiling tool (such as `perf <https://perf.wiki.kernel.org/index."
-"php/Main_Page>`_). A running process may create a file in the ``/tmp`` "
+"external profiling tool (such as `perf <https://perf.wiki.kernel.org/"
+"index.php/Main_Page>`_). A running process may create a file in the ``/tmp`` "
 "directory, which contains entries that can map a section of executable code "
 "to a name. This interface is described in the `documentation of the Linux "
-"Perf tool <https://git.kernel.org/pub/scm/linux/ kernel/git/torvalds/linux."
-"git/tree/tools/perf/Documentation/jit-interface.txt>`_."
+"Perf tool <https://git.kernel.org/pub/scm/linux/ kernel/git/torvalds/"
+"linux.git/tree/tools/perf/Documentation/jit-interface.txt>`_."
 msgstr ""
 
 #: ../Doc/c-api/perfmaps.rst:16
@@ -53,9 +54,9 @@ msgid ""
 "Open the ``/tmp/perf-$pid.map`` file, unless it's already opened, and create "
 "a lock to ensure thread-safe writes to the file (provided the writes are "
 "done through :c:func:`PyUnstable_WritePerfMapEntry`). Normally, there's no "
-"need to call this explicitly; just use :c:func:"
-"`PyUnstable_WritePerfMapEntry` and it will initialize the state on first "
-"call."
+"need to call this explicitly; just "
+"use :c:func:`PyUnstable_WritePerfMapEntry` and it will initialize the state "
+"on first call."
 msgstr ""
 
 #: ../Doc/c-api/perfmaps.rst:29
@@ -64,25 +65,38 @@ msgid ""
 "file, or ``-2`` on failure to create a lock. Check ``errno`` for more "
 "information about the cause of a failure."
 msgstr ""
+"Retorna ``0`` en caso de éxito, ``-1`` en caso de fallo al crear/abrir el "
+"fichero perf map, o ``-2`` en caso de fallo al crear un bloqueo. Comprueba "
+"``errno`` para más información sobre la causa de un fallo."
 
 #: ../Doc/c-api/perfmaps.rst:35
 msgid ""
 "Write one single entry to the ``/tmp/perf-$pid.map`` file. This function is "
 "thread safe. Here is what an example entry looks like::"
 msgstr ""
+"Escribe una única entrada en el fichero ``/tmp/perf-$pid.map``. Esta función "
+"es de hilo seguro. Aquí hay un ejemplo de entrada::"
 
+# creo que esto debe quedar igual. Es solo código fuente.
 #: ../Doc/c-api/perfmaps.rst:38
+#, fuzzy
 msgid ""
 "# address      size  name\n"
 "7f3529fcf759 b     py::bar:/run/t.py"
 msgstr ""
+"# address      size  name\n"
+"7f3529fcf759 b     py::bar:/run/t.py"
 
 #: ../Doc/c-api/perfmaps.rst:41
 msgid ""
 "Will call :c:func:`PyUnstable_PerfMapState_Init` before writing the entry, "
 "if the perf map file is not already opened. Returns ``0`` on success, or the "
 "same error codes as :c:func:`PyUnstable_PerfMapState_Init` on failure."
 msgstr ""
+"Llamará a :c:func:`PyUnstable_PerfMapState_Init` antes de escribir la "
+"entrada, si el fichero perf map no está ya abierto. Retorna ``0`` en caso de "
+"éxito, o los mismos códigos de error "
+"que :c:func:`PyUnstable_PerfMapState_Init` en caso de fallo."
 
 #: ../Doc/c-api/perfmaps.rst:47
 msgid ""
@@ -91,3 +105,8 @@ msgid ""
 "general, there shouldn't be a reason to explicitly call this, except to "
 "handle specific scenarios such as forking."
 msgstr ""
+"Cierra el fichero perf map abierto "
+"por :c:func:`PyUnstable_PerfMapState_Init`. Esto es llamado por el propio "
+"tiempo de ejecución durante el cierre del intérprete. En general, no debería "
+"haber una razón para llamar explícitamente a esto, excepto para manejar "
+"escenarios específicos como la bifurcación."