Fix incorrect truthyness for Enum types and literals #17337
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.
Fixes: #17333
This ensures
can_be_true
andcan_be_false
on enum literals depends on the specificEnum
fallback type behind theLiteral
, since__bool__
can be overriden like on any other type.Additionally typeops
true_only
andfalse_only
now respect the metaclass when looking up the return values of__bool__
and__len__
, which ensures that a defaultEnum
that doesn't override__bool__
is still considered always truthy.