All commit authors signed the Contributor License Agreement.

Is it possible to revert the IntEnum str change for the next 3.11 PATCH to not inherit from ReprEnum? Logging/code generation using the changed IntEnum.__str__ becomes much less informational, especially for interfaces that don't control how/where the IntEnums are defined and want to display the most informational str possible. I can see why the newly added StrEnum benefits greatly from ReprEnum but not so much for existing applications using IntEnum as informational str relying on the previous behavior.

Unfortunately, no. Using ReprEnum is basically a bug-fix for all the code switching from actual ints to IntEnum, as that code expects to have 5 and not SomeEnum.PENTAGON for the str value.

As for logging and error reporting, it's been my experience so far that that should almost always use repr.

@ethanfurman Thanks for the reply, will try to use these mixin techniques where I'm unable to use repr such as nested pretty printing. As for this docs change I'm unable to add the "skip issue" label myself to pass the checks

Thanks @gesslerpd for the PR, and @ethanfurman for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

GH-101518 is a backport of this pull request to the 3.11 branch.