Skip to content

Commit 2292896

Browse files
committed
Add everything to code blocks
1 parent cc5c2f0 commit 2292896

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

Doc/library/stdtypes.rst

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1460,7 +1460,7 @@ application).
14601460
lst.reverse()
14611461
lst.sort()
14621462
1463-
The following operations/methods are not atomic:
1463+
The following operations/methods are not fully atomic:
14641464

14651465
.. code-block::
14661466
:class: maybe
@@ -1469,6 +1469,11 @@ application).
14691469
lst.count(item)
14701470
item in lst
14711471
1472+
lst.extend(iterable)
1473+
lst += iterable
1474+
1475+
lst[i:j] = iterable
1476+
14721477
The :meth:`~list.index` and :meth:`~list.count` methods, and the ``in``
14731478
operator, iterate the list without holding a lock. They are safe to call
14741479
concurrently but may return results affected by concurrent modifications.
@@ -1482,9 +1487,9 @@ application).
14821487
applies to inplace concatenation of list with other iterables when using
14831488
``lst += iterable``.
14841489

1485-
Similarly, assigning to a list slice with ``lst[i:j] = obj`` is always
1486-
atomic with respect to the target list, but ``obj`` is only locked when it
1487-
is also a :class:`list`.
1490+
Similarly, assigning to a list slice with ``lst[i:j] = iterable`` is always
1491+
atomic with respect to the target list, but ``iterable`` is only locked when
1492+
it is also a :class:`list`.
14881493

14891494
Operations that involve multiple accesses, as well as iteration, are not
14901495
atomic. For example:

0 commit comments

Comments
 (0)