Fix note in Enum.__new__ docs (#118284)

This commit is contained in:
Philipp A 2024-04-26 16:06:53 +02:00 committed by GitHub
parent 463c20dae9
commit 5a4d3df2fa
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -279,7 +279,7 @@ Data Types
>>> Color.RED.value
1
Value of the member, can be set in :meth:`~object.__new__`.
Value of the member, can be set in :meth:`~Enum.__new__`.
.. note:: Enum member values
@ -299,7 +299,7 @@ Data Types
.. attribute:: Enum._value_
Value of the member, can be set in :meth:`~object.__new__`.
Value of the member, can be set in :meth:`~Enum.__new__`.
.. attribute:: Enum._order_
@ -407,8 +407,8 @@ Data Types
results in the call ``int('1a', 16)`` and a value of ``17`` for the member.
..note:: When writing a custom ``__new__``, do not use ``super().__new__`` --
call the appropriate ``__new__`` instead.
.. note:: When writing a custom ``__new__``, do not use ``super().__new__`` --
call the appropriate ``__new__`` instead.
.. method:: Enum.__repr__(self)
@ -827,7 +827,7 @@ Supported ``__dunder__`` names
:attr:`~EnumType.__members__` is a read-only ordered mapping of ``member_name``:``member``
items. It is only available on the class.
:meth:`~object.__new__`, if specified, must create and return the enum members;
:meth:`~Enum.__new__`, if specified, must create and return the enum members;
it is also a very good idea to set the member's :attr:`!_value_` appropriately.
Once all the members are created it is no longer used.