Skip to content

Traduccion howto logging cookbook #1665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 8, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Remove python-format from entries
  • Loading branch information
cmaureir committed Nov 26, 2021
commit 647c428dc137479264250bbf33de7cc0e1806227
9 changes: 0 additions & 9 deletions howto/logging-cookbook.po
Original file line number Diff line number Diff line change
Expand Up @@ -762,7 +762,6 @@ msgid "Use of alternative formatting styles"
msgstr "Uso de estilos de formato alternativos"

#: ../Doc/howto/logging-cookbook.rst:1049
#, python-format
msgid ""
"When logging was added to the Python standard library, the only way of "
"formatting messages with variable content was to use the %-formatting "
Expand Down Expand Up @@ -800,7 +799,6 @@ msgstr ""
"una sesión de consola de ejemplo para mostrar las posibilidades:"

#: ../Doc/howto/logging-cookbook.rst:1089
#, python-format
msgid ""
"Note that the formatting of logging messages for final output to logs is "
"completely independent of how an individual logging message is constructed. "
Expand All @@ -811,9 +809,7 @@ msgstr ""
"individual. Para eso todavía puede usar el formateo \"%\", como se muestra "
"aquí:"

# No entiendo este bloque en inglés ni en español :P
#: ../Doc/howto/logging-cookbook.rst:1097
#, python-format
msgid ""
"Logging calls (``logger.debug()``, ``logger.info()`` etc.) only take "
"positional parameters for the actual logging message itself, with keyword "
Expand Down Expand Up @@ -858,7 +854,6 @@ msgstr ""
"siguientes dos clases::"

#: ../Doc/howto/logging-cookbook.rst:1134
#, python-format
msgid ""
"Either of these can be used in place of a format string, to allow {}- or $-"
"formatting to be used to build the actual \"message\" part which appears in "
Expand Down Expand Up @@ -1535,7 +1530,6 @@ msgstr ""
"cómo se construye un mensaje de logging individual."

#: ../Doc/howto/logging-cookbook.rst:1970
#, python-format
msgid ""
"Logging calls (:meth:`~Logger.debug`, :meth:`~Logger.info` etc.) only take "
"positional parameters for the actual logging message itself, with keyword "
Expand Down Expand Up @@ -1564,7 +1558,6 @@ msgstr ""
"el código existente utilizarán cadenas de caracteres formato %."

#: ../Doc/howto/logging-cookbook.rst:1982
#, python-format
msgid ""
"There have been suggestions to associate format styles with specific "
"loggers, but that approach also runs into backward compatibility problems "
Expand Down Expand Up @@ -1593,7 +1586,6 @@ msgid "Using LogRecord factories"
msgstr "Uso de fábricas de LogRecord"

#: ../Doc/howto/logging-cookbook.rst:1995
#, python-format
msgid ""
"In Python 3.2, along with the :class:`~logging.Formatter` changes mentioned "
"above, the logging package gained the ability to allow users to set their "
Expand Down Expand Up @@ -1650,7 +1642,6 @@ msgstr ""
"formato real. Considere las siguientes dos clases:"

#: ../Doc/howto/logging-cookbook.rst:2038
#, python-format
msgid ""
"Either of these can be used in place of a format string, to allow {}- or $-"
"formatting to be used to build the actual \"message\" part which appears in "
Expand Down