Skip to content
Navigation Menu
{{ message }}
-
-
Notifications
You must be signed in to change notification settings - Fork 41
Expand file tree
/
Copy pathsynchronization.po
More file actions
407 lines (342 loc) · 12.8 KB
/
Copy pathsynchronization.po
File metadata and controls
407 lines (342 loc) · 12.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2026
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-05-08 18:34+0000\n"
"PO-Revision-Date: 2026-02-25 14:46+0000\n"
"Last-Translator: python-doc bot, 2026\n"
"Language-Team: Portuguese (Brazil) (https://app.transifex.com/python-doc/"
"teams/5390/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pt_BR\n"
"Plural-Forms: nplurals=3; plural=(n == 0 || n == 1) ? 0 : n != 0 && n % "
"1000000 == 0 ? 1 : 2;\n"
#: ../../c-api/synchronization.rst:6
msgid "Synchronization primitives"
msgstr "Primitivas de sincronização"
#: ../../c-api/synchronization.rst:8
msgid "The C-API provides a basic mutual exclusion lock."
msgstr ""
#: ../../c-api/synchronization.rst:12
msgid ""
"A mutual exclusion lock. The :c:type:`!PyMutex` should be initialized to "
"zero to represent the unlocked state. For example::"
msgstr ""
#: ../../c-api/synchronization.rst:15
msgid "PyMutex mutex = {0};"
msgstr ""
#: ../../c-api/synchronization.rst:17
msgid ""
"Instances of :c:type:`!PyMutex` should not be copied or moved. Both the "
"contents and address of a :c:type:`!PyMutex` are meaningful, and it must "
"remain at a fixed, writable location in memory."
msgstr ""
#: ../../c-api/synchronization.rst:23
msgid ""
"A :c:type:`!PyMutex` currently occupies one byte, but the size should be "
"considered unstable. The size may change in future Python releases without "
"a deprecation period."
msgstr ""
#: ../../c-api/synchronization.rst:31
msgid ""
"Lock mutex *m*. If another thread has already locked it, the calling thread "
"will block until the mutex is unlocked. While blocked, the thread will "
"temporarily detach the :term:`thread state <attached thread state>` if one "
"exists."
msgstr ""
#: ../../c-api/synchronization.rst:39
msgid ""
"Unlock mutex *m*. The mutex must be locked --- otherwise, the function will "
"issue a fatal error."
msgstr ""
#: ../../c-api/synchronization.rst:46
msgid "Returns non-zero if the mutex *m* is currently locked, zero otherwise."
msgstr ""
#: ../../c-api/synchronization.rst:50
msgid ""
"This function is intended for use in assertions and debugging only and "
"should not be used to make concurrency control decisions, as the lock state "
"may change immediately after the check."
msgstr ""
#: ../../c-api/synchronization.rst:59
msgid "Python critical section API"
msgstr ""
#: ../../c-api/synchronization.rst:61
msgid ""
"The critical section API provides a deadlock avoidance layer on top of per-"
"object locks for :term:`free-threaded <free threading>` CPython. They are "
"intended to replace reliance on the :term:`global interpreter lock`, and are "
"no-ops in versions of Python with the global interpreter lock."
msgstr ""
#: ../../c-api/synchronization.rst:66
msgid ""
"Critical sections are intended to be used for custom types implemented in C-"
"API extensions. They should generally not be used with built-in types like :"
"class:`list` and :class:`dict` because their public C-APIs already use "
"critical sections internally, with the notable exception of :c:func:"
"`PyDict_Next`, which requires critical section to be acquired externally."
msgstr ""
#: ../../c-api/synchronization.rst:73
msgid ""
"Critical sections avoid deadlocks by implicitly suspending active critical "
"sections, hence, they do not provide exclusive access such as provided by "
"traditional locks like :c:type:`PyMutex`. When a critical section is "
"started, the per-object lock for the object is acquired. If the code "
"executed inside the critical section calls C-API functions then it can "
"suspend the critical section thereby releasing the per-object lock, so other "
"threads can acquire the per-object lock for the same object."
msgstr ""
#: ../../c-api/synchronization.rst:81
msgid ""
"Variants that accept :c:type:`PyMutex` pointers rather than Python objects "
"are also available. Use these variants to start a critical section in a "
"situation where there is no :c:type:`PyObject` -- for example, when working "
"with a C type that does not extend or wrap :c:type:`PyObject` but still "
"needs to call into the C API in a manner that might lead to deadlocks."
msgstr ""
#: ../../c-api/synchronization.rst:89
msgid ""
"Operations that need to lock two objects at once must use :c:macro:"
"`Py_BEGIN_CRITICAL_SECTION2`. You *cannot* use nested critical sections to "
"lock more than one object at once, because the inner critical section may "
"suspend the outer critical sections. This API does not provide a way to "
"lock more than two objects at once."
msgstr ""
#: ../../c-api/synchronization.rst:95
msgid "Example usage::"
msgstr "Exemplo de uso::"
#: ../../c-api/synchronization.rst:97
msgid ""
"static PyObject *\n"
"set_field(MyObject *self, PyObject *value)\n"
"{\n"
" Py_BEGIN_CRITICAL_SECTION(self);\n"
" Py_SETREF(self->field, Py_XNewRef(value));\n"
" Py_END_CRITICAL_SECTION();\n"
" Py_RETURN_NONE;\n"
"}"
msgstr ""
#: ../../c-api/synchronization.rst:106
msgid ""
"In the above example, :c:macro:`Py_SETREF` calls :c:macro:`Py_DECREF`, which "
"can call arbitrary code through an object's deallocation function. The "
"critical section API avoids potential deadlocks due to reentrancy and lock "
"ordering by allowing the runtime to temporarily suspend the critical section "
"if the code triggered by the finalizer blocks and calls :c:func:"
"`PyEval_SaveThread`."
msgstr ""
#: ../../c-api/synchronization.rst:116
msgid ""
"Acquires the per-object lock for the object *op* and begins a critical "
"section."
msgstr ""
#: ../../c-api/synchronization.rst:119 ../../c-api/synchronization.rst:151
#: ../../c-api/synchronization.rst:181 ../../c-api/synchronization.rst:199
msgid ""
"In the free-threaded build, and when building for the :ref:`Stable ABI "
"<stable-abi>`, this macro expands to::"
msgstr ""
#: ../../c-api/synchronization.rst:122
msgid ""
"{\n"
" PyCriticalSection _py_cs;\n"
" PyCriticalSection_Begin(&_py_cs, (PyObject*)(op))"
msgstr ""
#: ../../c-api/synchronization.rst:126 ../../c-api/synchronization.rst:173
msgid "In the default build, this macro expands to ``{``."
msgstr ""
#: ../../c-api/synchronization.rst:132
msgid "Locks the mutex *m* and begins a critical section."
msgstr ""
#: ../../c-api/synchronization.rst:134 ../../c-api/synchronization.rst:167
msgid "In the free-threaded build, this macro expands to::"
msgstr ""
#: ../../c-api/synchronization.rst:136
msgid ""
"{\n"
" PyCriticalSection _py_cs;\n"
" PyCriticalSection_BeginMutex(&_py_cs, m)"
msgstr ""
#: ../../c-api/synchronization.rst:140
msgid ""
"Note that unlike :c:macro:`Py_BEGIN_CRITICAL_SECTION`, there is no cast for "
"the argument of the macro - it must be a :c:type:`PyMutex` pointer."
msgstr ""
#: ../../c-api/synchronization.rst:143 ../../c-api/synchronization.rst:191
msgid "On the default build, this macro expands to ``{``."
msgstr ""
#: ../../c-api/synchronization.rst:149
msgid "Ends the critical section and releases the per-object lock."
msgstr ""
#: ../../c-api/synchronization.rst:154
msgid ""
" PyCriticalSection_End(&_py_cs);\n"
"}"
msgstr ""
#: ../../c-api/synchronization.rst:157 ../../c-api/synchronization.rst:205
msgid "In the default build, this macro expands to ``}``."
msgstr ""
#: ../../c-api/synchronization.rst:163
msgid ""
"Acquires the per-object locks for the objects *a* and *b* and begins a "
"critical section. The locks are acquired in a consistent order (lowest "
"address first) to avoid lock ordering deadlocks."
msgstr ""
#: ../../c-api/synchronization.rst:169
msgid ""
"{\n"
" PyCriticalSection2 _py_cs2;\n"
" PyCriticalSection2_Begin(&_py_cs2, (PyObject*)(a), (PyObject*)(b))"
msgstr ""
#: ../../c-api/synchronization.rst:179
msgid "Locks the mutexes *m1* and *m2* and begins a critical section."
msgstr ""
#: ../../c-api/synchronization.rst:184
msgid ""
"{\n"
" PyCriticalSection2 _py_cs2;\n"
" PyCriticalSection2_BeginMutex(&_py_cs2, m1, m2)"
msgstr ""
#: ../../c-api/synchronization.rst:188
msgid ""
"Note that unlike :c:macro:`Py_BEGIN_CRITICAL_SECTION2`, there is no cast for "
"the arguments of the macro - they must be :c:type:`PyMutex` pointers."
msgstr ""
#: ../../c-api/synchronization.rst:197
msgid "Ends the critical section and releases the per-object locks."
msgstr ""
#: ../../c-api/synchronization.rst:202
msgid ""
" PyCriticalSection2_End(&_py_cs2);\n"
"}"
msgstr ""
#: ../../c-api/synchronization.rst:210
msgid "Low-level critical section API"
msgstr ""
#: ../../c-api/synchronization.rst:212
msgid ""
"The following functions and structs are exposed for cases where C macros are "
"not available."
msgstr ""
#: ../../c-api/synchronization.rst:220 ../../c-api/synchronization.rst:243
msgid ""
"To be used only as in the macro expansions listed :ref:`earlier in this "
"section <critical-section-macros>`."
msgstr ""
#: ../../c-api/synchronization.rst:223 ../../c-api/synchronization.rst:246
msgid ""
"In non-:term:`free-threaded <free threading>` builds of CPython, these "
"functions do nothing."
msgstr ""
#: ../../c-api/synchronization.rst:231
msgid ""
"To be used only as in the macro expansions listed :ref:`earlier in this "
"section <critical-section-macros>`. Note that the contents of the structures "
"are private and their meaning may change in future Python versions."
msgstr ""
#: ../../c-api/synchronization.rst:253
msgid "Legacy locking APIs"
msgstr ""
#: ../../c-api/synchronization.rst:255
msgid ""
"These APIs are obsolete since Python 3.13 with the introduction of :c:type:"
"`PyMutex`."
msgstr ""
#: ../../c-api/synchronization.rst:258
msgid "These APIs are now a simple wrapper around ``PyMutex``."
msgstr ""
#: ../../c-api/synchronization.rst:264
msgid "A pointer to a mutual exclusion lock."
msgstr ""
#: ../../c-api/synchronization.rst:269
msgid "The result of acquiring a lock with a timeout."
msgstr ""
#: ../../c-api/synchronization.rst:275
msgid "Failed to acquire the lock."
msgstr ""
#: ../../c-api/synchronization.rst:279
msgid "The lock was successfully acquired."
msgstr ""
#: ../../c-api/synchronization.rst:283
msgid "The lock was interrupted by a signal."
msgstr ""
#: ../../c-api/synchronization.rst:288
msgid "Allocate a new lock."
msgstr ""
#: ../../c-api/synchronization.rst:290
msgid ""
"On success, this function returns a lock; on failure, this function returns "
"``0`` without an exception set."
msgstr ""
#: ../../c-api/synchronization.rst:293 ../../c-api/synchronization.rst:305
#: ../../c-api/synchronization.rst:325 ../../c-api/synchronization.rst:343
#: ../../c-api/synchronization.rst:351
msgid "The caller does not need to hold an :term:`attached thread state`."
msgstr ""
#: ../../c-api/synchronization.rst:295
msgid ""
"This function now always uses :c:type:`PyMutex`. In prior versions, this "
"would use a lock provided by the operating system."
msgstr ""
#: ../../c-api/synchronization.rst:302
msgid ""
"Destroy *lock*. The lock should not be held by any thread when calling this."
msgstr ""
#: ../../c-api/synchronization.rst:310
msgid "Acquire *lock* with a timeout."
msgstr ""
#: ../../c-api/synchronization.rst:312
msgid ""
"This will wait for *microseconds* microseconds to acquire the lock. If the "
"timeout expires, this function returns :c:enumerator:`PY_LOCK_FAILURE`. If "
"*microseconds* is ``-1``, this will wait indefinitely until the lock has "
"been released."
msgstr ""
#: ../../c-api/synchronization.rst:317
msgid ""
"If *intr_flag* is ``1``, acquiring the lock may be interrupted by a signal, "
"in which case this function returns :c:enumerator:`PY_LOCK_INTR`. Upon "
"interruption, it's generally expected that the caller makes a call to :c:"
"func:`Py_MakePendingCalls` to propagate an exception to Python code."
msgstr ""
#: ../../c-api/synchronization.rst:322
msgid ""
"If the lock is successfully acquired, this function returns :c:enumerator:"
"`PY_LOCK_ACQUIRED`."
msgstr ""
#: ../../c-api/synchronization.rst:330
msgid "Acquire *lock*."
msgstr ""
#: ../../c-api/synchronization.rst:332
msgid ""
"If *waitflag* is ``1`` and another thread currently holds the lock, this "
"function will wait until the lock can be acquired and will always return "
"``1``."
msgstr ""
#: ../../c-api/synchronization.rst:336
msgid ""
"If *waitflag* is ``0`` and another thread holds the lock, this function will "
"not wait and instead return ``0``. If the lock is not held by any other "
"thread, then this function will acquire it and return ``1``."
msgstr ""
#: ../../c-api/synchronization.rst:340
msgid ""
"Unlike :c:func:`PyThread_acquire_lock_timed`, acquiring the lock cannot be "
"interrupted by a signal."
msgstr ""
#: ../../c-api/synchronization.rst:348
msgid ""
"Release *lock*. If *lock* is not held, then this function issues a fatal "
"error."
msgstr ""
You can’t perform that action at this time.