@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.12\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2024-02-16 14:13+0000\n "
15+ "POT-Creation-Date : 2024-03-15 14:13+0000\n "
1616"PO-Revision-Date : 2021-06-28 00:53+0000\n "
1717"Last-Translator : Maciej Olko <maciej.olko@gmail.com>, 2023\n "
1818"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -55,10 +55,12 @@ msgid "When to use logging"
5555msgstr ""
5656
5757msgid ""
58- "Logging provides a set of convenience functions for simple logging usage. "
59- "These are :func:`debug`, :func:`info`, :func:`warning`, :func:`error` and :"
60- "func:`critical`. To determine when to use logging, see the table below, "
61- "which states, for each of a set of common tasks, the best tool to use for it."
58+ "You can access logging functionality by creating a logger via ``logger = "
59+ "getLogger(__name__)``, and then calling the logger's :meth:`~Logger.debug`, :"
60+ "meth:`~Logger.info`, :meth:`~Logger.warning`, :meth:`~Logger.error` and :"
61+ "meth:`~Logger.critical` methods. To determine when to use logging, and to "
62+ "see which logger methods to use when, see the table below. It states, for "
63+ "each of a set of common tasks, the best tool to use for that task."
6264msgstr ""
6365
6466msgid "Task you want to perform"
@@ -80,8 +82,8 @@ msgid ""
8082msgstr ""
8183
8284msgid ""
83- ":func:`logging .info` (or :func:`logging .debug` for very detailed output for "
84- "diagnostic purposes)"
85+ "A logger's :meth:`~Logger .info` (or :meth:`~Logger .debug` method for very "
86+ "detailed output for diagnostic purposes)"
8587msgstr ""
8688
8789msgid "Issue a warning regarding a particular runtime event"
@@ -93,8 +95,8 @@ msgid ""
9395msgstr ""
9496
9597msgid ""
96- ":func:`logging .warning` if there is nothing the client application can do "
97- "about the situation, but the event should still be noted"
98+ "A logger's :meth:`~Logger .warning` method if there is nothing the client "
99+ "application can do about the situation, but the event should still be noted"
98100msgstr ""
99101
100102msgid "Report an error regarding a particular runtime event"
@@ -109,14 +111,15 @@ msgid ""
109111msgstr ""
110112
111113msgid ""
112- ":func:`logging.error`, :func:`logging.exception` or :func:`logging.critical` "
113- "as appropriate for the specific error and application domain"
114+ "A logger's :meth:`~Logger.error`, :meth:`~Logger.exception` or :meth:"
115+ "`~Logger.critical` method as appropriate for the specific error and "
116+ "application domain"
114117msgstr ""
115118
116119msgid ""
117- "The logging functions are named after the level or severity of the events "
118- "they are used to track. The standard levels and their applicability are "
119- "described below (in increasing order of severity):"
120+ "The logger methods are named after the level or severity of the events they "
121+ "are used to track. The standard levels and their applicability are described "
122+ "below (in increasing order of severity):"
120123msgstr ""
121124
122125msgid "Level"
@@ -188,11 +191,21 @@ msgid ""
188191"printed out on the console. The ``INFO`` message doesn't appear because the "
189192"default level is ``WARNING``. The printed message includes the indication of "
190193"the level and the description of the event provided in the logging call, i."
191- "e. 'Watch out!'. Don't worry about the 'root' part for now: it will be "
192- "explained later. The actual output can be formatted quite flexibly if you "
194+ "e. 'Watch out!'. The actual output can be formatted quite flexibly if you "
193195"need that; formatting options will also be explained later."
194196msgstr ""
195197
198+ msgid ""
199+ "Notice that in this example, we use functions directly on the ``logging`` "
200+ "module, like ``logging.debug``, rather than creating a logger and calling "
201+ "functions on it. These functions operation on the root logger, but can be "
202+ "useful as they will call :func:`~logging.basicConfig` for you if it has not "
203+ "been called yet, like in this example. In larger programs you'll usually "
204+ "want to control the logging configuration explicitly however - so for that "
205+ "reason as well as others, it's better to create loggers and call their "
206+ "methods."
207+ msgstr ""
208+
196209msgid "Logging to a file"
197210msgstr ""
198211
@@ -238,11 +251,9 @@ msgid ""
238251msgstr ""
239252
240253msgid ""
241- "The call to :func:`basicConfig` should come *before* any calls to :func:"
242- "`debug`, :func:`info`, etc. Otherwise, those functions will call :func:"
243- "`basicConfig` for you with the default options. As it's intended as a one-"
244- "off simple configuration facility, only the first call will actually do "
245- "anything: subsequent calls are effectively no-ops."
254+ "The call to :func:`basicConfig` should come *before* any calls to a logger's "
255+ "methods such as :meth:`~Logger.debug`, :meth:`~Logger.info`, etc. Otherwise, "
256+ "that logging event may not be handled in the desired manner."
246257msgstr ""
247258
248259msgid ""
@@ -257,27 +268,6 @@ msgid ""
257268"appended to, so the messages from earlier runs are lost."
258269msgstr ""
259270
260- msgid "Logging from multiple modules"
261- msgstr ""
262-
263- msgid ""
264- "If your program consists of multiple modules, here's an example of how you "
265- "could organize logging in it::"
266- msgstr ""
267-
268- msgid "If you run *myapp.py*, you should see this in *myapp.log*:"
269- msgstr ""
270-
271- msgid ""
272- "which is hopefully what you were expecting to see. You can generalize this "
273- "to multiple modules, using the pattern in *mylib.py*. Note that for this "
274- "simple usage pattern, you won't know, by looking in the log file, *where* in "
275- "your application your messages came from, apart from looking at the event "
276- "description. If you want to track the location of your messages, you'll need "
277- "to refer to the documentation beyond the tutorial level -- see :ref:`logging-"
278- "advanced-tutorial`."
279- msgstr ""
280-
281271msgid "Logging variable data"
282272msgstr ""
283273
0 commit comments