Skip to content

[3.9] bpo-41817: use new StrEnum to ensure all members are strings (GH-22348) #22367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 22, 2020

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Sep 22, 2020

  • use new StrEnum to ensure all members are strings
    (cherry picked from commit ea0711a)

Co-authored-by: Ethan Furman ethan@stoneleaf.us

https://bugs.python.org/issue41817

…H-22348)

* use new StrEnum to ensure all members are strings
(cherry picked from commit ea0711a)

Co-authored-by: Ethan Furman <ethan@stoneleaf.us>
@miss-islington
Copy link
Contributor Author

@ethanfurman: Status check is done, and it's a success ✅ .

`StrEnum` does not exist in 3.8, so use original `(str, enum.Enum)` bases.
@miss-islington miss-islington merged commit b38ad22 into python:3.9 Sep 22, 2020
@miss-islington miss-islington deleted the backport-ea0711a-3.9 branch September 22, 2020 18:31
@miss-islington
Copy link
Contributor Author

@ethanfurman: Status check is done, and it's a success ✅ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants