gh-111622: Fix doc for items views (#112051)
They are set-like even when some values are not hashable, but work even better when all are.
This commit is contained in:
parent
31ad7e061e
commit
e31d65e0b7
@ -4755,14 +4755,17 @@ support membership tests:
|
|||||||
|
|
||||||
.. versionadded:: 3.10
|
.. versionadded:: 3.10
|
||||||
|
|
||||||
Keys views are set-like since their entries are unique and :term:`hashable`. If all
|
Keys views are set-like since their entries are unique and :term:`hashable`.
|
||||||
values are hashable, so that ``(key, value)`` pairs are unique and hashable,
|
Items views also have set-like operations since the (key, value) pairs
|
||||||
then the items view is also set-like. (Values views are not treated as set-like
|
are unique and the keys are hashable.
|
||||||
|
If all values in an items view are hashable as well,
|
||||||
|
then the items view can interoperate with other sets.
|
||||||
|
(Values views are not treated as set-like
|
||||||
since the entries are generally not unique.) For set-like views, all of the
|
since the entries are generally not unique.) For set-like views, all of the
|
||||||
operations defined for the abstract base class :class:`collections.abc.Set` are
|
operations defined for the abstract base class :class:`collections.abc.Set` are
|
||||||
available (for example, ``==``, ``<``, or ``^``). While using set operators,
|
available (for example, ``==``, ``<``, or ``^``). While using set operators,
|
||||||
set-like views accept any iterable as the other operand, unlike sets which only
|
set-like views accept any iterable as the other operand,
|
||||||
accept sets as the input.
|
unlike sets which only accept sets as the input.
|
||||||
|
|
||||||
An example of dictionary view usage::
|
An example of dictionary view usage::
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user