-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ty] handle more enum.auto()
cases
#20541
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
Draft
thejchap
wants to merge
1
commit into
astral-sh:main
Choose a base branch
from
thejchap:thejchap/enum-auto2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+68
−5
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, I'm not sure we should be adding more special cases here. An enum class that uses
bytes
as a mixin isn't conceptually any different from an enum that usestuple
orlist
ordict
as a mixin, or a custom dataclass or customNamedTuple
as a mixin. Why should we treatbytes
andfloat
specially here?Rather than adding more special cases, I think we should have a generalised fallback logic that iterates through the MRO of the enum class to check whether it has a custom mixin that isn't
str
orint
. (Those two make sense to special-case, I think, because of the presence ofStrEnum
andIntEnum
in the stdlib. You can determine whether an element in the MRO is a "custom mixin" class by checking if it isn'tobject
and isn't a subclass ofenum.Enum
-- if both those conditions hold, I think we can treat it as a mixin class.) If the enum class has a custom mixin andauto()
is used to define the value of an enum member, we should probably infer the.value
of that enum member as just beingAny
, which would still be more accurate than what we have onmain
(even if it isn't very precise!). It seems pretty hard to predict whether the.value
property is going to give you an instance of the mixin or an integer:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this makes a lot more sense - thanks - didn't feel great about the explicit special cases after going down that road...