Skip to content

Commit aa69ad1

Browse files
[3.15] Fix unnumbered list item's text alignment in 'Thread safety for set objects' (GH-158261) (#158434)
Co-authored-by: Rafael Fontenelle <rffontenelle@users.noreply.github.com>
1 parent 5c000f0 commit aa69ad1

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

‎Doc/builtins/threadsafety.rst‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -408,19 +408,19 @@ as operands and always lock both objects:
408408
iterate through all the passed iterables and do the following:
409409

410410
* :meth:`set.update` and :meth:`set.union` lock both objects only when
411-
the other operand is a :class:`set`, :class:`frozenset`, or :class:`dict`.
411+
the other operand is a :class:`set`, :class:`frozenset`, or :class:`dict`.
412412
* :meth:`set.intersection` and :meth:`set.difference` always try to lock
413-
all objects.
413+
all objects.
414414

415415
:meth:`set.symmetric_difference` tries to lock both objects.
416416

417417
The update variants of the above methods also have some differences between
418418
them:
419419

420420
* :meth:`set.difference_update` and :meth:`set.intersection_update` try
421-
to lock all objects one-by-one.
421+
to lock all objects one-by-one.
422422
* :meth:`set.symmetric_difference_update` only locks the arguments if it is
423-
of type :class:`set`, :class:`frozenset`, or :class:`dict`.
423+
of type :class:`set`, :class:`frozenset`, or :class:`dict`.
424424

425425
The following methods always try to lock both objects:
426426

0 commit comments

Comments
 (0)