@@ -11,7 +11,7 @@ msgid ""
11
11
msgstr ""
12
12
"Project-Id-Version : Python 3.11\n "
13
13
"Report-Msgid-Bugs-To : \n "
14
- "POT-Creation-Date : 2024-02-16 16:40 +0000\n "
14
+ "POT-Creation-Date : 2024-03-15 16:48 +0000\n "
15
15
"PO-Revision-Date : 2023-05-24 02:11+0000\n "
16
16
"Last-Translator : Rafael Fontenelle <rffontenelle@gmail.com>, 2023\n "
17
17
"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -49,10 +49,12 @@ msgid "When to use logging"
49
49
msgstr ""
50
50
51
51
msgid ""
52
- "Logging provides a set of convenience functions for simple logging usage. "
53
- "These are :func:`debug`, :func:`info`, :func:`warning`, :func:`error` and :"
54
- "func:`critical`. To determine when to use logging, see the table below, "
55
- "which states, for each of a set of common tasks, the best tool to use for it."
52
+ "You can access logging functionality by creating a logger via ``logger = "
53
+ "getLogger(__name__)``, and then calling the logger's :meth:`~Logger.debug`, :"
54
+ "meth:`~Logger.info`, :meth:`~Logger.warning`, :meth:`~Logger.error` and :"
55
+ "meth:`~Logger.critical` methods. To determine when to use logging, and to "
56
+ "see which logger methods to use when, see the table below. It states, for "
57
+ "each of a set of common tasks, the best tool to use for that task."
56
58
msgstr ""
57
59
58
60
msgid "Task you want to perform"
@@ -74,8 +76,8 @@ msgid ""
74
76
msgstr ""
75
77
76
78
msgid ""
77
- ":func:`logging .info` (or :func:`logging .debug` for very detailed output for "
78
- "diagnostic purposes)"
79
+ "A logger's :meth:`~Logger .info` (or :meth:`~Logger .debug` method for very "
80
+ "detailed output for diagnostic purposes)"
79
81
msgstr ""
80
82
81
83
msgid "Issue a warning regarding a particular runtime event"
@@ -87,8 +89,8 @@ msgid ""
87
89
msgstr ""
88
90
89
91
msgid ""
90
- ":func:`logging .warning` if there is nothing the client application can do "
91
- "about the situation, but the event should still be noted"
92
+ "A logger's :meth:`~Logger .warning` method if there is nothing the client "
93
+ "application can do about the situation, but the event should still be noted"
92
94
msgstr ""
93
95
94
96
msgid "Report an error regarding a particular runtime event"
@@ -103,14 +105,15 @@ msgid ""
103
105
msgstr ""
104
106
105
107
msgid ""
106
- ":func:`logging.error`, :func:`logging.exception` or :func:`logging.critical` "
107
- "as appropriate for the specific error and application domain"
108
+ "A logger's :meth:`~Logger.error`, :meth:`~Logger.exception` or :meth:"
109
+ "`~Logger.critical` method as appropriate for the specific error and "
110
+ "application domain"
108
111
msgstr ""
109
112
110
113
msgid ""
111
- "The logging functions are named after the level or severity of the events "
112
- "they are used to track. The standard levels and their applicability are "
113
- "described below (in increasing order of severity):"
114
+ "The logger methods are named after the level or severity of the events they "
115
+ "are used to track. The standard levels and their applicability are described "
116
+ "below (in increasing order of severity):"
114
117
msgstr ""
115
118
116
119
msgid "Level"
@@ -182,11 +185,21 @@ msgid ""
182
185
"printed out on the console. The ``INFO`` message doesn't appear because the "
183
186
"default level is ``WARNING``. The printed message includes the indication of "
184
187
"the level and the description of the event provided in the logging call, i."
185
- "e. 'Watch out!'. Don't worry about the 'root' part for now: it will be "
186
- "explained later. The actual output can be formatted quite flexibly if you "
188
+ "e. 'Watch out!'. The actual output can be formatted quite flexibly if you "
187
189
"need that; formatting options will also be explained later."
188
190
msgstr ""
189
191
192
+ msgid ""
193
+ "Notice that in this example, we use functions directly on the ``logging`` "
194
+ "module, like ``logging.debug``, rather than creating a logger and calling "
195
+ "functions on it. These functions operation on the root logger, but can be "
196
+ "useful as they will call :func:`~logging.basicConfig` for you if it has not "
197
+ "been called yet, like in this example. In larger programs you'll usually "
198
+ "want to control the logging configuration explicitly however - so for that "
199
+ "reason as well as others, it's better to create loggers and call their "
200
+ "methods."
201
+ msgstr ""
202
+
190
203
msgid "Logging to a file"
191
204
msgstr ""
192
205
@@ -232,11 +245,9 @@ msgid ""
232
245
msgstr ""
233
246
234
247
msgid ""
235
- "The call to :func:`basicConfig` should come *before* any calls to :func:"
236
- "`debug`, :func:`info`, etc. Otherwise, those functions will call :func:"
237
- "`basicConfig` for you with the default options. As it's intended as a one-"
238
- "off simple configuration facility, only the first call will actually do "
239
- "anything: subsequent calls are effectively no-ops."
248
+ "The call to :func:`basicConfig` should come *before* any calls to a logger's "
249
+ "methods such as :meth:`~Logger.debug`, :meth:`~Logger.info`, etc. Otherwise, "
250
+ "that logging event may not be handled in the desired manner."
240
251
msgstr ""
241
252
242
253
msgid ""
@@ -251,27 +262,6 @@ msgid ""
251
262
"appended to, so the messages from earlier runs are lost."
252
263
msgstr ""
253
264
254
- msgid "Logging from multiple modules"
255
- msgstr ""
256
-
257
- msgid ""
258
- "If your program consists of multiple modules, here's an example of how you "
259
- "could organize logging in it::"
260
- msgstr ""
261
-
262
- msgid "If you run *myapp.py*, you should see this in *myapp.log*:"
263
- msgstr ""
264
-
265
- msgid ""
266
- "which is hopefully what you were expecting to see. You can generalize this "
267
- "to multiple modules, using the pattern in *mylib.py*. Note that for this "
268
- "simple usage pattern, you won't know, by looking in the log file, *where* in "
269
- "your application your messages came from, apart from looking at the event "
270
- "description. If you want to track the location of your messages, you'll need "
271
- "to refer to the documentation beyond the tutorial level -- see :ref:`logging-"
272
- "advanced-tutorial`."
273
- msgstr ""
274
-
275
265
msgid "Logging variable data"
276
266
msgstr ""
277
267
0 commit comments