René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unexpected behavior change in subclassing `Enum` class as of 3.11","articleBody":"I had a question regarding changes in subclassing `Enum` in 3.11. As of 3.11, if enum class has a mixin parent apart from `Enum` which has defined `__init__` or `__new__`, `member._value_` is set to be another instance of the mixin class\r\nunless user defines `__new__` in the enum class and set `_value_`. However user naturally expects `_value_` to be the value assigned to the member in class definition. In the example below\r\n\r\n```python\r\nclass mixin:\r\n  def __init__(self):\r\n    pass\r\n\r\nclass CustomEnum(mixin, Enum):\r\n  MEMBER = \"member\"\r\n```\r\n\r\n`CustomEnum.MEMBER` is an instance of mixin and `CustomEnum.MEMBER.value` is another instance of it (with different id), while it was expected that `CustomEnum.MEMBER.value` would be `\"member\"`. What has been the rationale for this change?\r\n\r\nBy the way, this change is not noted in python docs enumeration page.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-103495\n* gh-103514\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/sadra-barikbin","@type":"Person","name":"sadra-barikbin"},"datePublished":"2023-04-12T18:27:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/103479/cpython/issues/103479"}