gh-100458: Clarify Enum.__format__() change of mixed-in types in the whatsnew/3.11.rst#100387
gh-100458: Clarify Enum.__format__() change of mixed-in types in the whatsnew/3.11.rst#100387ethanfurman merged 7 commits into
Conversation
Sorry, something went wrong.
Co-authored-by: JosephSBoyle <48555120+JosephSBoyle@users.noreply.github.com>
|
@JosephSBoyle thank you! I've added your changes. Let me know if there is anything else needed from my side. Should I also open a PR against the 3.11 branch? |
Sorry, something went wrong.
|
@anze3db No need, once this is committed a backport PR will be automatically created. |
Sorry, something went wrong.
|
@JosephSBoyle there was more than a month of inactivity on this PR 😞 Anything I can do to help this getting merged? |
Sorry, something went wrong.
|
Hi @anze3db, I'm not a maintainer so perhaps this is a better question for @AlexWaygood. If the assigned reviewer is busy perhaps another reviewer can be assigned. |
Sorry, something went wrong.
|
Will this PR finds its way to the next version of Python? Further question: is this change documented here https://docs.python.org/3/library/enum.html ? I can't spot it... |
Sorry, something went wrong.
ethanfurman
left a comment
There was a problem hiding this comment.
My apologies -- I didn't get the [Submit Review] button pressed.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @ethanfurman: please review the changes made to this pull request. |
Sorry, something went wrong.
|
@ethanfurman just a friendly reminder to re-review this if you have the time, thanks! |
Sorry, something went wrong.
ethanfurman
left a comment
There was a problem hiding this comment.
Did some rewriting in an attempt to make it clearer.
Thoughts on the new changes?
Sorry, something went wrong.
|
Thanks @anze3db for the PR, and @ethanfurman for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
…n the whatsnew/3.11.rst (pythonGH-100387) (cherry picked from commit e665563) Co-authored-by: Anže Pečar <anze@pecar.me> Co-authored-by: JosephSBoyle <48555120+JosephSBoyle@users.noreply.github.com> Co-authored-by: Ethan Furman <ethan@stoneleaf.us>
* main: (463 commits) pythongh-104057: Fix direct invocation of test_super (python#104064) pythongh-87092: Expose assembler to unit tests (python#103988) pythongh-97696: asyncio eager tasks factory (python#102853) pythongh-84436: Immortalize in _PyStructSequence_InitBuiltinWithFlags() (pythongh-104054) pythongh-104057: Fix direct invocation of test_module (pythonGH-104059) pythongh-100458: Clarify Enum.__format__() change of mixed-in types in the whatsnew/3.11.rst (pythonGH-100387) pythongh-104018: disallow "z" format specifier in %-format of byte strings (pythonGH-104033) pythongh-104016: Fixed off by 1 error in f string tokenizer (python#104047) pythonGH-103629: Update Unpack's repr in compliance with PEP 692 (python#104048) pythongh-102799: replace sys.exc_info by sys.exception in inspect and traceback modules (python#104032) Fix typo in "expected" word in few source files (python#104034) pythongh-103824: fix use-after-free error in Parser/tokenizer.c (python#103993) pythongh-104035: Do not ignore user-defined `__{get,set}state__` in slotted frozen dataclasses (python#104041) pythongh-104028: Reduce object creation while calling callback function from gc (pythongh-104030) pythongh-104036: Fix direct invocation of test_typing (python#104037) pythongh-102213: Optimize the performance of `__getattr__` (pythonGH-103761) pythongh-103895: Improve how invalid `Exception.__notes__` are displayed (python#103897) Adjust expression from `==` to `!=` in alignment with the meaning of the paragraph. (pythonGH-104021) pythongh-88496: Fix IDLE test hang on macOS (python#104025) Improve int test coverage (python#104024) ...
Hey! 👋
Please correct me if I'm wrong, but the description of the change Enum.format() change in 3.11.rst doesn't seem accurate. The behavior in older Python versions was to return the member's value and not the member's key as is currently stated. Example code:
Running this on Python 3.10 prints:
And not
as the changelog states:
I noticed this because we were using the
strmixin with all Enum classes as a hack to get to the value without needing to writeFoo.BAR.value🫣 The new behavior in Python 3.11 broke our code and the current phrasing in the changelog makes it feel this was just a minor bugfix. Should this change be a bit more prominent since it can be a breaking change?By the way, thank you for adding
StrEnum, it's exactly what we needed!PS: Not sure if this needs a GitHub issue number, it's not exactly a typo, but it's still a minor change.
I'm happy to open an issue if needed.Issue linked below. Also let me know if I need to open the PR against any other branches as well. 🙇strorintMixin Breaking Change in Python 3.11 #100458