[3.13] Fix presentation of dataclasses' unsafe_hash
default value (GH-116532) (#135417)
Fix presentation of dataclasses' `unsafe_hash` default value (GH-116532) (cherry picked from commit 71f5fafdfb2e509f59cd584d45949c6496f88d41) Co-authored-by: Victorien <65306057+Viicos@users.noreply.github.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
This commit is contained in:
parent
8d07562849
commit
9a10b734f1
@ -121,8 +121,11 @@ Module contents
|
|||||||
:meth:`!__le__`, :meth:`!__gt__`, or :meth:`!__ge__`, then
|
:meth:`!__le__`, :meth:`!__gt__`, or :meth:`!__ge__`, then
|
||||||
:exc:`TypeError` is raised.
|
:exc:`TypeError` is raised.
|
||||||
|
|
||||||
- *unsafe_hash*: If ``False`` (the default), a :meth:`~object.__hash__` method
|
- *unsafe_hash*: If true, force ``dataclasses`` to create a
|
||||||
is generated according to how *eq* and *frozen* are set.
|
:meth:`~object.__hash__` method, even though it may not be safe to do so.
|
||||||
|
Otherwise, generate a :meth:`~object.__hash__` method according to how
|
||||||
|
*eq* and *frozen* are set.
|
||||||
|
The default value is ``False``.
|
||||||
|
|
||||||
:meth:`!__hash__` is used by built-in :meth:`hash`, and when objects are
|
:meth:`!__hash__` is used by built-in :meth:`hash`, and when objects are
|
||||||
added to hashed collections such as dictionaries and sets. Having a
|
added to hashed collections such as dictionaries and sets. Having a
|
||||||
|
Loading…
x
Reference in New Issue
Block a user