From d5d86e2145d11d6e844ee987780445c6ebce4309 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sat, 9 Mar 2024 01:56:58 +0100 Subject: [3.12] gh-105535 Document potential performance trap during enum creation (GH-107119) (GH116511) (cherry picked from commit 601f3a7b3391e9d219a8ec44a6c56d00ce584d2a) Co-authored-by: Nicolas A. Oyarzabal <79150521+nicky-eng@users.noreply.github.com> Co-authored-by: Ethan Furman Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- Doc/library/enum.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Doc/library/enum.rst b/Doc/library/enum.rst index 28dae42..bc5b3d7 100644 --- a/Doc/library/enum.rst +++ b/Doc/library/enum.rst @@ -269,6 +269,8 @@ 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 @@ -276,6 +278,11 @@ Data Types appropriate value will be chosen for you. See :class:`auto` for the details. + While mutable/unhashable values, such as :class:`dict`, :class:`list` or + a mutable :class:`~dataclasses.dataclass`, can be used, they will have a + quadratic performance impact during creation relative to the + total number of mutable/unhashable values in the enum. + .. attribute:: Enum._name_ Name of the member. -- cgit v0.12