2024-05-08 16:34:40 -03:00
|
|
|
:mod:`!enum` --- Support for enumerations
|
|
|
|
=========================================
|
2013-06-14 20:55:46 -03:00
|
|
|
|
|
|
|
.. module:: enum
|
2013-06-14 22:59:16 -03:00
|
|
|
:synopsis: Implementation of an enumeration class.
|
|
|
|
|
2018-07-07 16:01:25 -03:00
|
|
|
.. moduleauthor:: Ethan Furman <ethan@stoneleaf.us>
|
|
|
|
.. sectionauthor:: Barry Warsaw <barry@python.org>
|
|
|
|
.. sectionauthor:: Eli Bendersky <eliben@gmail.com>
|
|
|
|
.. sectionauthor:: Ethan Furman <ethan@stoneleaf.us>
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2013-12-20 15:20:49 -04:00
|
|
|
.. versionadded:: 3.4
|
|
|
|
|
2013-06-14 20:55:46 -03:00
|
|
|
**Source code:** :source:`Lib/enum.py`
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. sidebar:: Important
|
2020-09-14 17:32:44 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
This page contains the API reference information. For tutorial
|
|
|
|
information and discussion of more advanced topics, see
|
2020-09-14 17:32:44 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
* :ref:`Basic Tutorial <enum-basic-tutorial>`
|
|
|
|
* :ref:`Advanced Tutorial <enum-advanced-tutorial>`
|
|
|
|
* :ref:`Enum Cookbook <enum-cookbook>`
|
2014-02-06 12:13:14 -04:00
|
|
|
|
2021-06-18 17:15:46 -03:00
|
|
|
---------------
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
An enumeration:
|
2016-09-11 03:36:59 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
* is a set of symbolic names (members) bound to unique values
|
2022-11-12 14:39:47 -04:00
|
|
|
* can be iterated over to return its canonical (i.e. non-alias) members in
|
|
|
|
definition order
|
2021-06-09 13:03:55 -03:00
|
|
|
* uses *call* syntax to return members by value
|
|
|
|
* uses *index* syntax to return members by name
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Enumerations are created either by using :keyword:`class` syntax, or by
|
2021-03-31 01:17:26 -03:00
|
|
|
using function-call syntax::
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> from enum import Enum
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> # class syntax
|
|
|
|
>>> class Color(Enum):
|
|
|
|
... RED = 1
|
|
|
|
... GREEN = 2
|
|
|
|
... BLUE = 3
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> # functional syntax
|
|
|
|
>>> Color = Enum('Color', ['RED', 'GREEN', 'BLUE'])
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Even though we can use :keyword:`class` syntax to create Enums, Enums
|
2021-03-31 01:17:26 -03:00
|
|
|
are not normal Python classes. See
|
|
|
|
:ref:`How are Enums different? <enum-class-differences>` for more details.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. note:: Nomenclature
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2023-01-19 22:16:21 -04:00
|
|
|
- The class :class:`!Color` is an *enumeration* (or *enum*)
|
|
|
|
- The attributes :attr:`!Color.RED`, :attr:`!Color.GREEN`, etc., are
|
2022-01-17 11:18:13 -04:00
|
|
|
*enumeration members* (or *members*) and are functionally constants.
|
2021-03-31 01:17:26 -03:00
|
|
|
- The enum members have *names* and *values* (the name of
|
2023-01-19 22:16:21 -04:00
|
|
|
:attr:`!Color.RED` is ``RED``, the value of :attr:`!Color.BLUE` is
|
2021-03-31 01:17:26 -03:00
|
|
|
``3``, etc.)
|
2013-07-18 21:05:39 -03:00
|
|
|
|
2021-06-18 17:15:46 -03:00
|
|
|
---------------
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Module Contents
|
|
|
|
---------------
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`EnumType`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
The ``type`` for Enum and its subclasses.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`Enum`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Base class for creating enumerated constants.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`IntEnum`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Base class for creating enumerated constants that are also
|
2021-06-18 17:15:46 -03:00
|
|
|
subclasses of :class:`int`. (`Notes`_)
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`StrEnum`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Base class for creating enumerated constants that are also
|
2021-06-18 17:15:46 -03:00
|
|
|
subclasses of :class:`str`. (`Notes`_)
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`Flag`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Base class for creating enumerated constants that can be combined using
|
|
|
|
the bitwise operations without losing their :class:`Flag` membership.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`IntFlag`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Base class for creating enumerated constants that can be combined using
|
|
|
|
the bitwise operators without losing their :class:`IntFlag` membership.
|
2021-06-18 17:15:46 -03:00
|
|
|
:class:`IntFlag` members are also subclasses of :class:`int`. (`Notes`_)
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2022-10-21 19:36:41 -03:00
|
|
|
:class:`ReprEnum`
|
|
|
|
|
|
|
|
Used by :class:`IntEnum`, :class:`StrEnum`, and :class:`IntFlag`
|
|
|
|
to keep the :class:`str() <str>` of the mixed-in type.
|
|
|
|
|
2021-06-09 13:03:55 -03:00
|
|
|
:class:`EnumCheck`
|
|
|
|
|
|
|
|
An enumeration with the values ``CONTINUOUS``, ``NAMED_FLAGS``, and
|
|
|
|
``UNIQUE``, for use with :func:`verify` to ensure various constraints
|
|
|
|
are met by a given enumeration.
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`FlagBoundary`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
An enumeration with the values ``STRICT``, ``CONFORM``, ``EJECT``, and
|
|
|
|
``KEEP`` which allows for more fine-grained control over how invalid values
|
|
|
|
are dealt with in an enumeration.
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:class:`auto`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Instances are replaced with an appropriate value for Enum members.
|
|
|
|
:class:`StrEnum` defaults to the lower-cased version of the member name,
|
|
|
|
while other Enums default to 1 and increase from there.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2022-02-12 00:21:38 -04:00
|
|
|
:func:`~enum.property`
|
2016-08-05 20:03:16 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Allows :class:`Enum` members to have attributes without conflicting with
|
2023-04-18 20:19:23 -03:00
|
|
|
member names. The ``value`` and ``name`` attributes are implemented this
|
|
|
|
way.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
:func:`unique`
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Enum class decorator that ensures only one name is bound to any one value.
|
2013-06-28 23:37:17 -03:00
|
|
|
|
2021-06-09 13:03:55 -03:00
|
|
|
:func:`verify`
|
|
|
|
|
|
|
|
Enum class decorator that checks user-selectable constraints on an
|
|
|
|
enumeration.
|
|
|
|
|
2022-05-06 04:16:22 -03:00
|
|
|
:func:`member`
|
|
|
|
|
2022-05-15 12:34:52 -03:00
|
|
|
Make ``obj`` a member. Can be used as a decorator.
|
2022-05-06 04:16:22 -03:00
|
|
|
|
|
|
|
:func:`nonmember`
|
|
|
|
|
2022-05-15 12:34:52 -03:00
|
|
|
Do not make ``obj`` a member. Can be used as a decorator.
|
2022-05-06 04:16:22 -03:00
|
|
|
|
2022-10-21 19:36:41 -03:00
|
|
|
:func:`global_enum`
|
|
|
|
|
|
|
|
Modify the :class:`str() <str>` and :func:`repr` of an enum
|
2023-04-03 18:57:42 -03:00
|
|
|
to show its members as belonging to the module instead of its class,
|
|
|
|
and export the enum members to the global namespace.
|
2022-10-21 19:36:41 -03:00
|
|
|
|
|
|
|
:func:`show_flag_values`
|
|
|
|
|
|
|
|
Return a list of all power-of-two integers contained in a flag.
|
|
|
|
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. versionadded:: 3.6 ``Flag``, ``IntFlag``, ``auto``
|
2022-10-21 19:36:41 -03:00
|
|
|
.. versionadded:: 3.11 ``StrEnum``, ``EnumCheck``, ``ReprEnum``, ``FlagBoundary``, ``property``, ``member``, ``nonmember``, ``global_enum``, ``show_flag_values``
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-06-18 17:15:46 -03:00
|
|
|
---------------
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Data Types
|
|
|
|
----------
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2014-02-08 15:36:27 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: EnumType
|
2014-02-08 15:36:27 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
*EnumType* is the :term:`metaclass` for *enum* enumerations. It is possible
|
|
|
|
to subclass *EnumType* -- see :ref:`Subclassing EnumType <enumtype-examples>`
|
|
|
|
for details.
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
``EnumType`` is responsible for setting the correct :meth:`!__repr__`,
|
2023-01-19 22:16:21 -04:00
|
|
|
:meth:`!__str__`, :meth:`!__format__`, and :meth:`!__reduce__` methods on the
|
2022-01-17 11:18:13 -04:00
|
|
|
final *enum*, as well as creating the enum members, properly handling
|
|
|
|
duplicates, providing iteration over the enum class, etc.
|
|
|
|
|
2024-03-03 15:32:32 -04:00
|
|
|
.. method:: EnumType.__call__(cls, value, names=None, *, module=None, qualname=None, type=None, start=1, boundary=None)
|
2023-04-03 18:57:42 -03:00
|
|
|
|
|
|
|
This method is called in two different ways:
|
|
|
|
|
|
|
|
* to look up an existing member:
|
|
|
|
|
|
|
|
:cls: The enum class being called.
|
|
|
|
:value: The value to lookup.
|
|
|
|
|
|
|
|
* to use the ``cls`` enum to create a new enum (only if the existing enum
|
|
|
|
does not have any members):
|
|
|
|
|
|
|
|
:cls: The enum class being called.
|
|
|
|
:value: The name of the new Enum to create.
|
|
|
|
:names: The names/values of the members for the new Enum.
|
|
|
|
:module: The name of the module the new Enum is created in.
|
|
|
|
:qualname: The actual location in the module where this Enum can be found.
|
|
|
|
:type: A mix-in type for the new Enum.
|
|
|
|
:start: The first integer value for the Enum (used by :class:`auto`).
|
|
|
|
:boundary: How to handle out-of-range values from bit operations (:class:`Flag` only).
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__contains__(cls, member)
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns ``True`` if member belongs to the ``cls``::
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> some_var = Color.RED
|
|
|
|
>>> some_var in Color
|
|
|
|
True
|
2023-10-24 14:30:13 -03:00
|
|
|
>>> Color.RED.value in Color
|
|
|
|
True
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2023-10-24 14:30:13 -03:00
|
|
|
.. versionchanged:: 3.12
|
2021-04-27 17:05:08 -03:00
|
|
|
|
2023-10-24 14:30:13 -03:00
|
|
|
Before Python 3.12, a ``TypeError`` is raised if a
|
2021-04-27 17:05:08 -03:00
|
|
|
non-Enum-member is used in a containment check.
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__dir__(cls)
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns ``['__class__', '__doc__', '__members__', '__module__']`` and the
|
2022-01-17 11:18:13 -04:00
|
|
|
names of the members in *cls*::
|
2015-01-15 02:31:50 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> dir(Color)
|
2022-01-17 11:18:13 -04:00
|
|
|
['BLUE', 'GREEN', 'RED', '__class__', '__contains__', '__doc__', '__getitem__', '__init_subclass__', '__iter__', '__len__', '__members__', '__module__', '__name__', '__qualname__']
|
2015-01-15 02:31:50 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__getitem__(cls, name)
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
Returns the Enum member in *cls* matching *name*, or raises a :exc:`KeyError`::
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color['BLUE']
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.BLUE: 3>
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__iter__(cls)
|
2014-03-03 16:42:52 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns each member in *cls* in definition order::
|
2014-09-17 00:35:55 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> list(Color)
|
2022-01-17 11:18:13 -04:00
|
|
|
[<Color.RED: 1>, <Color.GREEN: 2>, <Color.BLUE: 3>]
|
2014-09-17 23:23:14 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__len__(cls)
|
2014-02-08 15:36:27 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns the number of member in *cls*::
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> len(Color)
|
|
|
|
3
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
.. attribute:: EnumType.__members__
|
|
|
|
|
|
|
|
Returns a mapping of every enum name to its member, including aliases
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: EnumType.__reversed__(cls)
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns each member in *cls* in reverse definition order::
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> list(reversed(Color))
|
2022-01-17 11:18:13 -04:00
|
|
|
[<Color.BLUE: 3>, <Color.GREEN: 2>, <Color.RED: 1>]
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
.. method:: EnumType._add_alias_
|
|
|
|
|
|
|
|
Adds a new name as an alias to an existing member. Raises a
|
|
|
|
:exc:`NameError` if the name is already assigned to a different member.
|
|
|
|
|
|
|
|
.. method:: EnumType._add_value_alias_
|
|
|
|
|
|
|
|
Adds a new value as an alias to an existing member. Raises a
|
|
|
|
:exc:`ValueError` if the value is already linked with a different member.
|
|
|
|
|
2023-08-22 11:34:18 -03:00
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
Before 3.11 ``EnumType`` was called ``EnumMeta``, which is still available as an alias.
|
2023-08-22 11:34:18 -03:00
|
|
|
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: Enum
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
*Enum* is the base class for all *enum* enumerations.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: Enum.name
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
The name used to define the ``Enum`` member::
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.BLUE.name
|
|
|
|
'BLUE'
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: Enum.value
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
The value given to the ``Enum`` member::
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.RED.value
|
|
|
|
1
|
2020-09-22 17:00:07 -03:00
|
|
|
|
2024-04-26 11:06:53 -03:00
|
|
|
Value of the member, can be set in :meth:`~Enum.__new__`.
|
2024-03-08 15:22:17 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. note:: Enum member values
|
2020-09-22 17:00:07 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
Member values can be anything: :class:`int`, :class:`str`, etc. If
|
2021-03-31 01:17:26 -03:00
|
|
|
the exact value is unimportant you may use :class:`auto` instances and an
|
2022-11-05 22:01:08 -03:00
|
|
|
appropriate value will be chosen for you. See :class:`auto` for the
|
|
|
|
details.
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2024-03-08 15:22:17 -04:00
|
|
|
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.
|
|
|
|
|
2024-02-09 02:40:28 -04:00
|
|
|
.. attribute:: Enum._name_
|
|
|
|
|
|
|
|
Name of the member.
|
|
|
|
|
|
|
|
.. attribute:: Enum._value_
|
|
|
|
|
2024-04-26 11:06:53 -03:00
|
|
|
Value of the member, can be set in :meth:`~Enum.__new__`.
|
2024-02-09 02:40:28 -04:00
|
|
|
|
|
|
|
.. attribute:: Enum._order_
|
|
|
|
|
|
|
|
No longer used, kept for backward compatibility.
|
|
|
|
(class attribute, removed during class creation).
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: Enum._ignore_
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
``_ignore_`` is only used during creation and is removed from the
|
2022-01-17 11:18:13 -04:00
|
|
|
enumeration once creation is complete.
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
``_ignore_`` is a list of names that will not become members, and whose
|
|
|
|
names will also be removed from the completed enumeration. See
|
|
|
|
:ref:`TimePeriod <enum-time-period>` for an example.
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: Enum.__dir__(self)
|
|
|
|
|
|
|
|
Returns ``['__class__', '__doc__', '__module__', 'name', 'value']`` and
|
2022-01-17 11:18:13 -04:00
|
|
|
any public methods defined on *self.__class__*::
|
2021-03-31 01:17:26 -03:00
|
|
|
|
|
|
|
>>> from datetime import date
|
|
|
|
>>> class Weekday(Enum):
|
|
|
|
... MONDAY = 1
|
|
|
|
... TUESDAY = 2
|
|
|
|
... WEDNESDAY = 3
|
|
|
|
... THURSDAY = 4
|
|
|
|
... FRIDAY = 5
|
|
|
|
... SATURDAY = 6
|
|
|
|
... SUNDAY = 7
|
|
|
|
... @classmethod
|
|
|
|
... def today(cls):
|
2021-07-26 18:35:09 -03:00
|
|
|
... print('today is %s' % cls(date.today().isoweekday()).name)
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> dir(Weekday.SATURDAY)
|
2022-01-17 11:18:13 -04:00
|
|
|
['__class__', '__doc__', '__eq__', '__hash__', '__module__', 'name', 'today', 'value']
|
2021-03-31 01:17:26 -03:00
|
|
|
|
|
|
|
.. method:: Enum._generate_next_value_(name, start, count, last_values)
|
|
|
|
|
|
|
|
:name: The name of the member being defined (e.g. 'RED').
|
|
|
|
:start: The start value for the Enum; the default is 1.
|
|
|
|
:count: The number of members currently defined, not including this one.
|
|
|
|
:last_values: A list of the previous values.
|
|
|
|
|
|
|
|
A *staticmethod* that is used to determine the next value returned by
|
|
|
|
:class:`auto`::
|
|
|
|
|
|
|
|
>>> from enum import auto
|
|
|
|
>>> class PowersOfThree(Enum):
|
|
|
|
... @staticmethod
|
|
|
|
... def _generate_next_value_(name, start, count, last_values):
|
2022-12-11 19:20:59 -04:00
|
|
|
... return 3 ** (count + 1)
|
2021-03-31 01:17:26 -03:00
|
|
|
... FIRST = auto()
|
|
|
|
... SECOND = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> PowersOfThree.SECOND.value
|
2022-12-11 19:20:59 -04:00
|
|
|
9
|
2021-03-31 01:17:26 -03:00
|
|
|
|
2024-03-03 15:32:32 -04:00
|
|
|
.. method:: Enum.__init__(self, *args, **kwds)
|
gh-114071: [Enum] update docs and code for tuples/subclasses (GH-114871)
Update documentation with `__new__` and `__init__` entries.
Support use of `auto()` in tuple subclasses on member assignment lines. Previously, auto() was only supported on the member definition line either solo or as part of a tuple:
RED = auto()
BLUE = auto(), 'azul'
However, since Python itself supports using tuple subclasses where tuples are expected, e.g.:
from collections import namedtuple
T = namedtuple('T', 'first second third')
def test(one, two, three):
print(one, two, three)
test(*T(4, 5, 6))
# 4 5 6
it made sense to also support tuple subclasses in enum definitions.
2024-02-04 11:22:55 -04:00
|
|
|
|
|
|
|
By default, does nothing. If multiple values are given in the member
|
|
|
|
assignment, those values become separate arguments to ``__init__``; e.g.
|
|
|
|
|
|
|
|
>>> from enum import Enum
|
|
|
|
>>> class Weekday(Enum):
|
|
|
|
... MONDAY = 1, 'Mon'
|
|
|
|
|
|
|
|
``Weekday.__init__()`` would be called as ``Weekday.__init__(self, 1, 'Mon')``
|
|
|
|
|
2024-03-03 15:32:32 -04:00
|
|
|
.. method:: Enum.__init_subclass__(cls, **kwds)
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
A *classmethod* that is used to further configure subsequent subclasses.
|
|
|
|
By default, does nothing.
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: Enum._missing_(cls, value)
|
|
|
|
|
|
|
|
A *classmethod* for looking up values not found in *cls*. By default it
|
|
|
|
does nothing, but can be overridden to implement custom search behavior::
|
|
|
|
|
|
|
|
>>> from enum import StrEnum
|
|
|
|
>>> class Build(StrEnum):
|
|
|
|
... DEBUG = auto()
|
|
|
|
... OPTIMIZED = auto()
|
|
|
|
... @classmethod
|
|
|
|
... def _missing_(cls, value):
|
|
|
|
... value = value.lower()
|
|
|
|
... for member in cls:
|
|
|
|
... if member.value == value:
|
|
|
|
... return member
|
|
|
|
... return None
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Build.DEBUG.value
|
|
|
|
'debug'
|
|
|
|
>>> Build('deBUG')
|
2022-01-17 11:18:13 -04:00
|
|
|
<Build.DEBUG: 'debug'>
|
2021-03-31 01:17:26 -03:00
|
|
|
|
2024-03-03 15:32:32 -04:00
|
|
|
.. method:: Enum.__new__(cls, *args, **kwds)
|
gh-114071: [Enum] update docs and code for tuples/subclasses (GH-114871)
Update documentation with `__new__` and `__init__` entries.
Support use of `auto()` in tuple subclasses on member assignment lines. Previously, auto() was only supported on the member definition line either solo or as part of a tuple:
RED = auto()
BLUE = auto(), 'azul'
However, since Python itself supports using tuple subclasses where tuples are expected, e.g.:
from collections import namedtuple
T = namedtuple('T', 'first second third')
def test(one, two, three):
print(one, two, three)
test(*T(4, 5, 6))
# 4 5 6
it made sense to also support tuple subclasses in enum definitions.
2024-02-04 11:22:55 -04:00
|
|
|
|
|
|
|
By default, doesn't exist. If specified, either in the enum class
|
|
|
|
definition or in a mixin class (such as ``int``), all values given
|
|
|
|
in the member assignment will be passed; e.g.
|
|
|
|
|
|
|
|
>>> from enum import Enum
|
2024-05-07 08:42:18 -03:00
|
|
|
>>> class MyIntEnum(int, Enum):
|
|
|
|
... TWENTYSIX = '1a', 16
|
gh-114071: [Enum] update docs and code for tuples/subclasses (GH-114871)
Update documentation with `__new__` and `__init__` entries.
Support use of `auto()` in tuple subclasses on member assignment lines. Previously, auto() was only supported on the member definition line either solo or as part of a tuple:
RED = auto()
BLUE = auto(), 'azul'
However, since Python itself supports using tuple subclasses where tuples are expected, e.g.:
from collections import namedtuple
T = namedtuple('T', 'first second third')
def test(one, two, three):
print(one, two, three)
test(*T(4, 5, 6))
# 4 5 6
it made sense to also support tuple subclasses in enum definitions.
2024-02-04 11:22:55 -04:00
|
|
|
|
2024-05-07 08:42:18 -03:00
|
|
|
results in the call ``int('1a', 16)`` and a value of ``26`` for the member.
|
gh-114071: [Enum] update docs and code for tuples/subclasses (GH-114871)
Update documentation with `__new__` and `__init__` entries.
Support use of `auto()` in tuple subclasses on member assignment lines. Previously, auto() was only supported on the member definition line either solo or as part of a tuple:
RED = auto()
BLUE = auto(), 'azul'
However, since Python itself supports using tuple subclasses where tuples are expected, e.g.:
from collections import namedtuple
T = namedtuple('T', 'first second third')
def test(one, two, three):
print(one, two, three)
test(*T(4, 5, 6))
# 4 5 6
it made sense to also support tuple subclasses in enum definitions.
2024-02-04 11:22:55 -04:00
|
|
|
|
2024-05-07 08:42:18 -03:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
When writing a custom ``__new__``, do not use ``super().__new__`` --
|
|
|
|
call the appropriate ``__new__`` instead.
|
2024-02-28 19:17:49 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: Enum.__repr__(self)
|
|
|
|
|
|
|
|
Returns the string used for *repr()* calls. By default, returns the
|
2022-01-17 11:18:13 -04:00
|
|
|
*Enum* name, member name, and value, but can be overridden::
|
2021-03-31 01:17:26 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
>>> class OtherStyle(Enum):
|
|
|
|
... ALTERNATE = auto()
|
|
|
|
... OTHER = auto()
|
|
|
|
... SOMETHING_ELSE = auto()
|
2021-03-31 01:17:26 -03:00
|
|
|
... def __repr__(self):
|
|
|
|
... cls_name = self.__class__.__name__
|
2022-01-17 11:18:13 -04:00
|
|
|
... return f'{cls_name}.{self.name}'
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2022-01-17 11:18:13 -04:00
|
|
|
>>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
|
|
|
|
(OtherStyle.ALTERNATE, 'OtherStyle.ALTERNATE', 'OtherStyle.ALTERNATE')
|
2021-03-31 01:17:26 -03:00
|
|
|
|
|
|
|
.. method:: Enum.__str__(self)
|
|
|
|
|
|
|
|
Returns the string used for *str()* calls. By default, returns the
|
2022-01-17 11:18:13 -04:00
|
|
|
*Enum* name and member name, but can be overridden::
|
2021-03-31 01:17:26 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
>>> class OtherStyle(Enum):
|
|
|
|
... ALTERNATE = auto()
|
|
|
|
... OTHER = auto()
|
|
|
|
... SOMETHING_ELSE = auto()
|
2021-03-31 01:17:26 -03:00
|
|
|
... def __str__(self):
|
2022-01-17 11:18:13 -04:00
|
|
|
... return f'{self.name}'
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2022-01-17 11:18:13 -04:00
|
|
|
>>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
|
|
|
|
(<OtherStyle.ALTERNATE: 1>, 'ALTERNATE', 'ALTERNATE')
|
|
|
|
|
|
|
|
.. method:: Enum.__format__(self)
|
|
|
|
|
|
|
|
Returns the string used for *format()* and *f-string* calls. By default,
|
2022-12-04 15:49:31 -04:00
|
|
|
returns :meth:`__str__` return value, but can be overridden::
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
>>> class OtherStyle(Enum):
|
|
|
|
... ALTERNATE = auto()
|
|
|
|
... OTHER = auto()
|
|
|
|
... SOMETHING_ELSE = auto()
|
|
|
|
... def __format__(self, spec):
|
|
|
|
... return f'{self.name}'
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2022-01-17 11:18:13 -04:00
|
|
|
>>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
|
|
|
|
(<OtherStyle.ALTERNATE: 1>, 'OtherStyle.ALTERNATE', 'ALTERNATE')
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. note::
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Using :class:`auto` with :class:`Enum` results in integers of increasing value,
|
|
|
|
starting with ``1``.
|
2016-09-02 20:32:32 -03:00
|
|
|
|
2022-12-06 17:43:41 -04:00
|
|
|
.. versionchanged:: 3.12 Added :ref:`enum-dataclass-support`
|
|
|
|
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: IntEnum
|
2016-09-02 20:32:32 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
*IntEnum* is the same as :class:`Enum`, but its members are also integers and can be
|
2021-03-31 01:17:26 -03:00
|
|
|
used anywhere that an integer can be used. If any integer operation is performed
|
|
|
|
with an *IntEnum* member, the resulting value loses its enumeration status.
|
|
|
|
|
|
|
|
>>> from enum import IntEnum
|
2023-05-19 14:46:20 -03:00
|
|
|
>>> class Number(IntEnum):
|
2021-03-31 01:17:26 -03:00
|
|
|
... ONE = 1
|
|
|
|
... TWO = 2
|
|
|
|
... THREE = 3
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2023-05-19 14:46:20 -03:00
|
|
|
>>> Number.THREE
|
|
|
|
<Number.THREE: 3>
|
|
|
|
>>> Number.ONE + Number.TWO
|
2021-03-31 01:17:26 -03:00
|
|
|
3
|
2023-05-19 14:46:20 -03:00
|
|
|
>>> Number.THREE + 5
|
2021-03-31 01:17:26 -03:00
|
|
|
8
|
2023-05-19 14:46:20 -03:00
|
|
|
>>> Number.THREE == 3
|
2021-03-31 01:17:26 -03:00
|
|
|
True
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. note::
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Using :class:`auto` with :class:`IntEnum` results in integers of increasing
|
|
|
|
value, starting with ``1``.
|
|
|
|
|
2023-01-19 22:16:21 -04:00
|
|
|
.. versionchanged:: 3.11 :meth:`~object.__str__` is now :meth:`!int.__str__` to
|
2022-01-17 11:18:13 -04:00
|
|
|
better support the *replacement of existing constants* use-case.
|
2023-01-19 22:16:21 -04:00
|
|
|
:meth:`~object.__format__` was already :meth:`!int.__format__` for that same reason.
|
2016-09-02 03:55:19 -03:00
|
|
|
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: StrEnum
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
``StrEnum`` is the same as :class:`Enum`, but its members are also strings and can be used
|
2021-03-31 01:17:26 -03:00
|
|
|
in most of the same places that a string can be used. The result of any string
|
|
|
|
operation performed on or with a *StrEnum* member is not part of the enumeration.
|
2013-06-14 20:55:46 -03:00
|
|
|
|
2022-11-12 14:39:47 -04:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
There are places in the stdlib that check for an exact :class:`str`
|
|
|
|
instead of a :class:`str` subclass (i.e. ``type(unknown) == str``
|
|
|
|
instead of ``isinstance(unknown, str)``), and in those locations you
|
|
|
|
will need to use ``str(StrEnum.member)``.
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. note::
|
2013-07-18 21:05:39 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Using :class:`auto` with :class:`StrEnum` results in the lower-cased member
|
|
|
|
name as the value.
|
2013-07-18 21:05:39 -03:00
|
|
|
|
2022-11-12 14:39:47 -04:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
:meth:`~object.__str__` is :meth:`!str.__str__` to better support the
|
|
|
|
*replacement of existing constants* use-case. :meth:`~object.__format__` is likewise
|
|
|
|
:meth:`!str.__format__` for that same reason.
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. versionadded:: 3.11
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: Flag
|
2018-01-22 11:56:37 -04:00
|
|
|
|
gh-114071: [Enum] update docs and code for tuples/subclasses (GH-114871)
Update documentation with `__new__` and `__init__` entries.
Support use of `auto()` in tuple subclasses on member assignment lines. Previously, auto() was only supported on the member definition line either solo or as part of a tuple:
RED = auto()
BLUE = auto(), 'azul'
However, since Python itself supports using tuple subclasses where tuples are expected, e.g.:
from collections import namedtuple
T = namedtuple('T', 'first second third')
def test(one, two, three):
print(one, two, three)
test(*T(4, 5, 6))
# 4 5 6
it made sense to also support tuple subclasses in enum definitions.
2024-02-04 11:22:55 -04:00
|
|
|
``Flag`` is the same as :class:`Enum`, but its members support the bitwise
|
|
|
|
operators ``&`` (*AND*), ``|`` (*OR*), ``^`` (*XOR*), and ``~`` (*INVERT*);
|
2024-06-14 14:25:35 -03:00
|
|
|
the results of those operations are (aliases of) members of the enumeration.
|
2018-01-22 11:56:37 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __contains__(self, value)
|
2018-01-22 11:56:37 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns *True* if value is in self::
|
2018-01-22 11:56:37 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> from enum import Flag, auto
|
|
|
|
>>> class Color(Flag):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> purple = Color.RED | Color.BLUE
|
|
|
|
>>> white = Color.RED | Color.GREEN | Color.BLUE
|
|
|
|
>>> Color.GREEN in purple
|
|
|
|
False
|
|
|
|
>>> Color.GREEN in white
|
|
|
|
True
|
|
|
|
>>> purple in white
|
|
|
|
True
|
|
|
|
>>> white in purple
|
|
|
|
False
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __iter__(self):
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2022-11-12 14:39:47 -04:00
|
|
|
Returns all contained non-alias members::
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> list(Color.RED)
|
2022-01-17 11:18:13 -04:00
|
|
|
[<Color.RED: 1>]
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> list(purple)
|
2022-01-17 11:18:13 -04:00
|
|
|
[<Color.RED: 1>, <Color.BLUE: 4>]
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2024-02-06 21:28:01 -04:00
|
|
|
.. versionadded:: 3.11
|
2022-11-12 14:39:47 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __len__(self):
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns number of members in flag::
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> len(Color.GREEN)
|
|
|
|
1
|
|
|
|
>>> len(white)
|
|
|
|
3
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __bool__(self):
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns *True* if any members in flag, *False* otherwise::
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> bool(Color.GREEN)
|
|
|
|
True
|
|
|
|
>>> bool(white)
|
|
|
|
True
|
|
|
|
>>> black = Color(0)
|
|
|
|
>>> bool(black)
|
|
|
|
False
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __or__(self, other)
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns current flag binary or'ed with other::
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.RED | Color.GREEN
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.RED|GREEN: 3>
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __and__(self, other)
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns current flag binary and'ed with other::
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> purple & white
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.RED|BLUE: 5>
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> purple & Color.GREEN
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color: 0>
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __xor__(self, other)
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
Returns current flag binary xor'ed with other::
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> purple ^ white
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.GREEN: 2>
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> purple ^ Color.GREEN
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.RED|GREEN|BLUE: 7>
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. method:: __invert__(self):
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
Returns all the flags in *type(self)* that are not in *self*::
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> ~white
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color: 0>
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> ~purple
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.GREEN: 2>
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> ~Color.RED
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.GREEN|BLUE: 6>
|
|
|
|
|
|
|
|
.. method:: _numeric_repr_
|
|
|
|
|
|
|
|
Function used to format any remaining unnamed numeric values. Default is
|
|
|
|
the value's repr; common choices are :func:`hex` and :func:`oct`.
|
|
|
|
|
|
|
|
.. note::
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Using :class:`auto` with :class:`Flag` results in integers that are powers
|
|
|
|
of two, starting with ``1``.
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
.. versionchanged:: 3.11 The *repr()* of zero-valued flags has changed. It
|
2024-06-17 13:01:15 -03:00
|
|
|
is now:
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
>>> Color(0) # doctest: +SKIP
|
|
|
|
<Color: 0>
|
2015-11-20 17:12:26 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: IntFlag
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
``IntFlag`` is the same as :class:`Flag`, but its members are also integers and can be
|
2021-03-31 01:17:26 -03:00
|
|
|
used anywhere that an integer can be used.
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> from enum import IntFlag, auto
|
|
|
|
>>> class Color(IntFlag):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.RED & 2
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color: 0>
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.RED | 2
|
2022-01-17 11:18:13 -04:00
|
|
|
<Color.RED|GREEN: 3>
|
2020-09-21 21:23:13 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
If any integer operation is performed with an *IntFlag* member, the result is
|
|
|
|
not an *IntFlag*::
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> Color.RED + 2
|
|
|
|
3
|
2016-01-15 19:01:33 -04:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
If a :class:`Flag` operation is performed with an *IntFlag* member and:
|
2016-01-15 19:01:33 -04:00
|
|
|
|
2023-10-11 17:24:12 -03:00
|
|
|
* the result is a valid *IntFlag*: an *IntFlag* is returned
|
2023-10-25 14:32:09 -03:00
|
|
|
* the result is not a valid *IntFlag*: the result depends on the :class:`FlagBoundary` setting
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
The :func:`repr()` of unnamed zero-valued flags has changed. It is now:
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
>>> Color(0)
|
|
|
|
<Color: 0>
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
|
|
|
Using :class:`auto` with :class:`IntFlag` results in integers that are powers
|
|
|
|
of two, starting with ``1``.
|
|
|
|
|
2022-11-12 14:39:47 -04:00
|
|
|
.. versionchanged:: 3.11
|
|
|
|
|
|
|
|
:meth:`~object.__str__` is now :meth:`!int.__str__` to better support the
|
|
|
|
*replacement of existing constants* use-case. :meth:`~object.__format__` was
|
|
|
|
already :meth:`!int.__format__` for that same reason.
|
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
Inversion of an :class:`!IntFlag` now returns a positive value that is the
|
2022-11-12 14:39:47 -04:00
|
|
|
union of all flags not in the given flag, rather than a negative value.
|
|
|
|
This matches the existing :class:`Flag` behavior.
|
2016-09-02 03:55:19 -03:00
|
|
|
|
2022-10-21 19:36:41 -03:00
|
|
|
.. class:: ReprEnum
|
|
|
|
|
2023-01-17 06:51:56 -04:00
|
|
|
:class:`!ReprEnum` uses the :meth:`repr() <Enum.__repr__>` of :class:`Enum`,
|
2022-10-21 19:36:41 -03:00
|
|
|
but the :class:`str() <str>` of the mixed-in data type:
|
|
|
|
|
2023-10-11 17:24:12 -03:00
|
|
|
* :meth:`!int.__str__` for :class:`IntEnum` and :class:`IntFlag`
|
|
|
|
* :meth:`!str.__str__` for :class:`StrEnum`
|
2022-10-21 19:36:41 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
Inherit from :class:`!ReprEnum` to keep the :class:`str() <str>` / :func:`format`
|
2022-10-21 19:36:41 -03:00
|
|
|
of the mixed-in data type instead of using the
|
|
|
|
:class:`Enum`-default :meth:`str() <Enum.__str__>`.
|
|
|
|
|
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2021-06-09 13:03:55 -03:00
|
|
|
.. class:: EnumCheck
|
|
|
|
|
|
|
|
*EnumCheck* contains the options used by the :func:`verify` decorator to ensure
|
2022-01-17 11:18:13 -04:00
|
|
|
various constraints; failed constraints result in a :exc:`ValueError`.
|
2021-06-09 13:03:55 -03:00
|
|
|
|
|
|
|
.. attribute:: UNIQUE
|
|
|
|
|
|
|
|
Ensure that each value has only one name::
|
|
|
|
|
|
|
|
>>> from enum import Enum, verify, UNIQUE
|
|
|
|
>>> @verify(UNIQUE)
|
|
|
|
... class Color(Enum):
|
|
|
|
... RED = 1
|
|
|
|
... GREEN = 2
|
|
|
|
... BLUE = 3
|
|
|
|
... CRIMSON = 1
|
|
|
|
Traceback (most recent call last):
|
|
|
|
...
|
|
|
|
ValueError: aliases found in <enum 'Color'>: CRIMSON -> RED
|
|
|
|
|
|
|
|
|
|
|
|
.. attribute:: CONTINUOUS
|
|
|
|
|
|
|
|
Ensure that there are no missing values between the lowest-valued member
|
|
|
|
and the highest-valued member::
|
|
|
|
|
|
|
|
>>> from enum import Enum, verify, CONTINUOUS
|
|
|
|
>>> @verify(CONTINUOUS)
|
|
|
|
... class Color(Enum):
|
|
|
|
... RED = 1
|
|
|
|
... GREEN = 2
|
|
|
|
... BLUE = 5
|
|
|
|
Traceback (most recent call last):
|
|
|
|
...
|
|
|
|
ValueError: invalid enum 'Color': missing values 3, 4
|
|
|
|
|
|
|
|
.. attribute:: NAMED_FLAGS
|
|
|
|
|
|
|
|
Ensure that any flag groups/masks contain only named flags -- useful when
|
2022-12-04 15:49:31 -04:00
|
|
|
values are specified instead of being generated by :func:`auto`::
|
2021-06-09 13:03:55 -03:00
|
|
|
|
|
|
|
>>> from enum import Flag, verify, NAMED_FLAGS
|
|
|
|
>>> @verify(NAMED_FLAGS)
|
|
|
|
... class Color(Flag):
|
|
|
|
... RED = 1
|
|
|
|
... GREEN = 2
|
|
|
|
... BLUE = 4
|
|
|
|
... WHITE = 15
|
|
|
|
... NEON = 31
|
|
|
|
Traceback (most recent call last):
|
|
|
|
...
|
2021-06-15 22:51:19 -03:00
|
|
|
ValueError: invalid Flag 'Color': aliases WHITE and NEON are missing combined values of 0x18 [use enum.show_flag_values(value) for details]
|
2021-06-09 13:03:55 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. note::
|
2021-06-09 13:03:55 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
CONTINUOUS and NAMED_FLAGS are designed to work with integer-valued members.
|
2021-06-09 13:03:55 -03:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. versionadded:: 3.11
|
2021-06-09 13:03:55 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: FlagBoundary
|
2013-09-28 02:58:06 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
``FlagBoundary`` controls how out-of-range values are handled in :class:`Flag` and its
|
2021-03-31 01:17:26 -03:00
|
|
|
subclasses.
|
2016-08-20 04:00:52 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: STRICT
|
2016-09-18 17:15:41 -03:00
|
|
|
|
2023-04-13 12:24:33 -03:00
|
|
|
Out-of-range values cause a :exc:`ValueError` to be raised. This is the
|
|
|
|
default for :class:`Flag`::
|
2016-09-18 17:15:41 -03:00
|
|
|
|
2023-02-17 17:36:47 -04:00
|
|
|
>>> from enum import Flag, STRICT, auto
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> class StrictFlag(Flag, boundary=STRICT):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> StrictFlag(2**2 + 2**4)
|
|
|
|
Traceback (most recent call last):
|
|
|
|
...
|
2022-01-17 11:18:13 -04:00
|
|
|
ValueError: <flag 'StrictFlag'> invalid value 20
|
2021-03-31 01:17:26 -03:00
|
|
|
given 0b0 10100
|
|
|
|
allowed 0b0 00111
|
2016-09-18 17:15:41 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: CONFORM
|
2016-09-18 17:15:41 -03:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
Out-of-range values have invalid values removed, leaving a valid :class:`Flag`
|
2023-04-13 12:24:33 -03:00
|
|
|
value::
|
2020-09-22 17:00:07 -03:00
|
|
|
|
2023-02-17 17:36:47 -04:00
|
|
|
>>> from enum import Flag, CONFORM, auto
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> class ConformFlag(Flag, boundary=CONFORM):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> ConformFlag(2**2 + 2**4)
|
2022-01-17 11:18:13 -04:00
|
|
|
<ConformFlag.BLUE: 4>
|
2020-09-22 17:00:07 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: EJECT
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
Out-of-range values lose their :class:`Flag` membership and revert to :class:`int`.
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2023-02-17 17:36:47 -04:00
|
|
|
>>> from enum import Flag, EJECT, auto
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> class EjectFlag(Flag, boundary=EJECT):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> EjectFlag(2**2 + 2**4)
|
|
|
|
20
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. attribute:: KEEP
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2023-10-25 14:32:09 -03:00
|
|
|
Out-of-range values are kept, and the :class:`Flag` membership is kept.
|
2023-04-03 18:57:42 -03:00
|
|
|
This is the default for :class:`IntFlag`::
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2023-02-17 17:36:47 -04:00
|
|
|
>>> from enum import Flag, KEEP, auto
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> class KeepFlag(Flag, boundary=KEEP):
|
|
|
|
... RED = auto()
|
|
|
|
... GREEN = auto()
|
|
|
|
... BLUE = auto()
|
2022-12-08 23:31:19 -04:00
|
|
|
...
|
2021-03-31 01:17:26 -03:00
|
|
|
>>> KeepFlag(2**2 + 2**4)
|
2022-01-17 11:18:13 -04:00
|
|
|
<KeepFlag.BLUE|16: 20>
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-07-27 12:20:00 -03:00
|
|
|
.. versionadded:: 3.11
|
2021-05-14 02:59:53 -03:00
|
|
|
|
2021-06-18 17:15:46 -03:00
|
|
|
---------------
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
Supported ``__dunder__`` names
|
|
|
|
""""""""""""""""""""""""""""""
|
|
|
|
|
2023-01-19 22:16:21 -04:00
|
|
|
:attr:`~EnumType.__members__` is a read-only ordered mapping of ``member_name``:``member``
|
2022-01-17 11:18:13 -04:00
|
|
|
items. It is only available on the class.
|
|
|
|
|
2024-04-26 11:06:53 -03:00
|
|
|
:meth:`~Enum.__new__`, if specified, must create and return the enum members;
|
2023-12-05 12:27:36 -04:00
|
|
|
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.
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
|
|
|
|
Supported ``_sunder_`` names
|
|
|
|
""""""""""""""""""""""""""""
|
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
- :meth:`~EnumType._add_alias_` -- adds a new name as an alias to an existing
|
|
|
|
member.
|
|
|
|
- :meth:`~EnumType._add_value_alias_` -- adds a new value as an alias to an
|
|
|
|
existing member.
|
|
|
|
- :attr:`~Enum._name_` -- name of the member
|
|
|
|
- :attr:`~Enum._value_` -- value of the member; can be set in ``__new__``
|
|
|
|
- :meth:`~Enum._missing_` -- a lookup function used when a value is not found;
|
|
|
|
may be overridden
|
|
|
|
- :attr:`~Enum._ignore_` -- a list of names, either as a :class:`list` or a
|
|
|
|
:class:`str`, that will not be transformed into members, and will be removed
|
|
|
|
from the final class
|
2024-02-09 02:40:28 -04:00
|
|
|
- :attr:`~Enum._order_` -- no longer used, kept for backward
|
|
|
|
compatibility (class attribute, removed during class creation)
|
2023-12-05 12:27:36 -04:00
|
|
|
- :meth:`~Enum._generate_next_value_` -- used to get an appropriate value for
|
|
|
|
an enum member; may be overridden
|
2022-01-17 11:18:13 -04:00
|
|
|
|
2023-10-11 17:24:12 -03:00
|
|
|
.. note::
|
2022-01-17 11:18:13 -04:00
|
|
|
|
2023-12-05 12:27:36 -04:00
|
|
|
For standard :class:`Enum` classes the next value chosen is the highest
|
|
|
|
value seen incremented by one.
|
2022-01-17 11:18:13 -04:00
|
|
|
|
2023-10-11 17:24:12 -03:00
|
|
|
For :class:`Flag` classes the next value chosen will be the next highest
|
2023-12-05 12:27:36 -04:00
|
|
|
power-of-two.
|
2022-01-17 11:18:13 -04:00
|
|
|
|
2024-05-07 15:11:18 -03:00
|
|
|
- While ``_sunder_`` names are generally reserved for the further development
|
|
|
|
of the :class:`Enum` class and can not be used, some are explicitly allowed:
|
|
|
|
|
|
|
|
- ``_repr_*`` (e.g. ``_repr_html_``), as used in `IPython's rich display`_
|
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. versionadded:: 3.6 ``_missing_``, ``_order_``, ``_generate_next_value_``
|
|
|
|
.. versionadded:: 3.7 ``_ignore_``
|
2024-05-07 15:11:18 -03:00
|
|
|
.. versionadded:: 3.13 ``_add_alias_``, ``_add_value_alias_``, ``_repr_*``
|
|
|
|
.. _`IPython's rich display`: https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
---------------
|
|
|
|
|
2021-10-05 18:48:44 -03:00
|
|
|
Utilities and Decorators
|
|
|
|
------------------------
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. class:: auto
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
*auto* can be used in place of a value. If used, the *Enum* machinery will
|
2023-10-25 14:32:09 -03:00
|
|
|
call an :class:`Enum`'s :meth:`~Enum._generate_next_value_` to get an appropriate value.
|
|
|
|
For :class:`Enum` and :class:`IntEnum` that appropriate value will be the last value plus
|
|
|
|
one; for :class:`Flag` and :class:`IntFlag` it will be the first power-of-two greater
|
|
|
|
than the highest value; for :class:`StrEnum` it will be the lower-cased version of
|
2023-01-03 18:08:50 -04:00
|
|
|
the member's name. Care must be taken if mixing *auto()* with manually
|
|
|
|
specified values.
|
2022-11-05 22:01:08 -03:00
|
|
|
|
|
|
|
*auto* instances are only resolved when at the top level of an assignment:
|
|
|
|
|
2023-10-11 17:24:12 -03:00
|
|
|
* ``FIRST = auto()`` will work (auto() is replaced with ``1``);
|
|
|
|
* ``SECOND = auto(), -2`` will work (auto is replaced with ``2``, so ``2, -2`` is
|
2024-01-18 05:23:15 -04:00
|
|
|
used to create the ``SECOND`` enum member;
|
2023-10-11 17:24:12 -03:00
|
|
|
* ``THREE = [auto(), -3]`` will *not* work (``<auto instance>, -3`` is used to
|
|
|
|
create the ``THREE`` enum member)
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-12-05 06:35:31 -04:00
|
|
|
.. versionchanged:: 3.11.1
|
|
|
|
|
|
|
|
In prior versions, ``auto()`` had to be the only thing
|
|
|
|
on the assignment line to work properly.
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
``_generate_next_value_`` can be overridden to customize the values used by
|
|
|
|
*auto*.
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2023-01-12 11:40:29 -04:00
|
|
|
.. note:: in 3.13 the default ``_generate_next_value_`` will always return
|
2022-06-23 03:20:24 -03:00
|
|
|
the highest member value incremented by 1, and will fail if any
|
|
|
|
member is an incompatible type.
|
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. decorator:: property
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
A decorator similar to the built-in *property*, but specifically for
|
|
|
|
enumerations. It allows member attributes to have the same names as members
|
|
|
|
themselves.
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. note:: the *property* and the member must be defined in separate classes;
|
|
|
|
for example, the *value* and *name* attributes are defined in the
|
|
|
|
*Enum* class, and *Enum* subclasses can define members with the
|
|
|
|
names ``value`` and ``name``.
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. versionadded:: 3.11
|
2021-05-14 02:59:53 -03:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
.. decorator:: unique
|
bpo-38250: [Enum] single-bit flags are canonical (GH-24215)
Flag members are now divided by one-bit verses multi-bit, with multi-bit being treated as aliases. Iterating over a flag only returns the contained single-bit flags.
Iterating, repr(), and str() show members in definition order.
When constructing combined-member flags, any extra integer values are either discarded (CONFORM), turned into ints (EJECT) or treated as errors (STRICT). Flag classes can specify which of those three behaviors is desired:
>>> class Test(Flag, boundary=CONFORM):
... ONE = 1
... TWO = 2
...
>>> Test(5)
<Test.ONE: 1>
Besides the three above behaviors, there is also KEEP, which should not be used unless necessary -- for example, _convert_ specifies KEEP as there are flag sets in the stdlib that are incomplete and/or inconsistent (e.g. ssl.Options). KEEP will, as the name suggests, keep all bits; however, iterating over a flag with extra bits will only return the canonical flags contained, not the extra bits.
Iteration is now in member definition order. If member definition order
matches increasing value order, then a more efficient method of flag
decomposition is used; otherwise, sort() is called on the results of
that method to get definition order.
``re`` module:
repr() has been modified to support as closely as possible its previous
output; the big difference is that inverted flags cannot be output as
before because the inversion operation now always returns the comparable
positive result; i.e.
re.A|re.I|re.M|re.S is ~(re.L|re.U|re.S|re.T|re.DEBUG)
in both of the above terms, the ``value`` is 282.
re's tests have been updated to reflect the modifications to repr().
2021-01-25 18:26:19 -04:00
|
|
|
|
2021-03-31 01:17:26 -03:00
|
|
|
A :keyword:`class` decorator specifically for enumerations. It searches an
|
2023-01-19 22:16:21 -04:00
|
|
|
enumeration's :attr:`~EnumType.__members__`, gathering any aliases it finds; if any are
|
2021-03-31 01:17:26 -03:00
|
|
|
found :exc:`ValueError` is raised with the details::
|
|
|
|
|
|
|
|
>>> from enum import Enum, unique
|
|
|
|
>>> @unique
|
|
|
|
... class Mistake(Enum):
|
|
|
|
... ONE = 1
|
|
|
|
... TWO = 2
|
|
|
|
... THREE = 3
|
|
|
|
... FOUR = 3
|
|
|
|
...
|
|
|
|
Traceback (most recent call last):
|
|
|
|
...
|
|
|
|
ValueError: duplicate values found in <enum 'Mistake'>: FOUR -> THREE
|
2021-06-09 13:03:55 -03:00
|
|
|
|
|
|
|
.. decorator:: verify
|
|
|
|
|
|
|
|
A :keyword:`class` decorator specifically for enumerations. Members from
|
|
|
|
:class:`EnumCheck` are used to specify which constraints should be checked
|
|
|
|
on the decorated enumeration.
|
|
|
|
|
2022-01-17 11:18:13 -04:00
|
|
|
.. versionadded:: 3.11
|
2021-06-18 17:15:46 -03:00
|
|
|
|
2022-05-06 04:16:22 -03:00
|
|
|
.. decorator:: member
|
|
|
|
|
2022-05-06 06:53:00 -03:00
|
|
|
A decorator for use in enums: its target will become a member.
|
2022-05-06 04:16:22 -03:00
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
|
|
|
.. decorator:: nonmember
|
|
|
|
|
2022-05-06 06:53:00 -03:00
|
|
|
A decorator for use in enums: its target will not become a member.
|
2022-05-06 04:16:22 -03:00
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
2022-10-21 19:36:41 -03:00
|
|
|
.. decorator:: global_enum
|
|
|
|
|
|
|
|
A decorator to change the :class:`str() <str>` and :func:`repr` of an enum
|
|
|
|
to show its members as belonging to the module instead of its class.
|
|
|
|
Should only be used when the enum members are exported
|
|
|
|
to the module global namespace (see :class:`re.RegexFlag` for an example).
|
|
|
|
|
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
|
|
|
.. function:: show_flag_values(value)
|
|
|
|
|
|
|
|
Return a list of all power-of-two integers contained in a flag *value*.
|
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
2021-06-18 17:15:46 -03:00
|
|
|
---------------
|
|
|
|
|
|
|
|
Notes
|
|
|
|
-----
|
|
|
|
|
|
|
|
:class:`IntEnum`, :class:`StrEnum`, and :class:`IntFlag`
|
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
These three enum types are designed to be drop-in replacements for existing
|
|
|
|
integer- and string-based values; as such, they have extra limitations:
|
2021-06-18 17:15:46 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
- ``__str__`` uses the value and not the name of the enum member
|
2021-06-18 17:15:46 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
- ``__format__``, because it uses ``__str__``, will also use the value of
|
|
|
|
the enum member instead of its name
|
2021-06-18 17:15:46 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
If you do not need/want those limitations, you can either create your own
|
|
|
|
base class by mixing in the ``int`` or ``str`` type yourself::
|
2021-06-18 17:15:46 -03:00
|
|
|
|
2022-12-04 15:49:31 -04:00
|
|
|
>>> from enum import Enum
|
|
|
|
>>> class MyIntEnum(int, Enum):
|
|
|
|
... pass
|
2022-01-17 11:18:13 -04:00
|
|
|
|
|
|
|
or you can reassign the appropriate :meth:`str`, etc., in your enum::
|
|
|
|
|
2023-02-02 16:12:57 -04:00
|
|
|
>>> from enum import Enum, IntEnum
|
2022-12-04 15:49:31 -04:00
|
|
|
>>> class MyIntEnum(IntEnum):
|
2023-02-02 16:12:57 -04:00
|
|
|
... __str__ = Enum.__str__
|