8000 gh-105535 Document potential performance trap during enum creation by nicky-eng · Pull Request #107119 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

gh-105535 Document potential performance trap during enum creation 8000 #107119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Mar 8, 2024
Prev Previous commit
Next Next commit
Merge branch 'main' into fix-issue-105535
  • Loading branch information
ethanfurman authored Mar 4, 2024
commit ee2a9623c7e36817b754ca06bb808457c513b960
8 changes: 7 additions & 1 deletion Doc/library/enum.rst
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,9 @@ Data Types

>>> Color.RED.value
1


Value of the member, can be set in :meth:`~object.__new__`.

.. note:: Enum member values

Member values can be anything: :class:`int`, :class:`str`, etc. If
Expand All @@ -291,6 +293,10 @@ Data Types
quadratic performance impact during creation relative to the
total number of mutable/unhashable values in the enum.

.. attribute:: Enum._order_

No longer used, kept for backward compatibility.
(class attribute, removed during class creation).

.. attribute:: Enum._ignore_

Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.
0