Repository navigation
Spec change: clarify that assert_type() uses equivalence #45
Description
Activity
Just a linguistic nit: the subject is unclear to me — does it describe an existing condition that’s undesirable, or a desirable improvement, or something else?
I see it as a clarification of the spec: the current wording in the spec is not clear about how assert_type() behaves; my proposed change makes it more precise.
Cool! If it was my issue I’d work “clarify” in the title somehow. :-)
Reacted by Jelle Zijlstra- changed the title
[-]Spec change: assert_type() uses equivalence[/-][+]Spec change: clarify that assert_type() uses equivalence[/+]on Jun 29, 2025 Accepted, thanks!
Please consider the proposed spec change in python/typing#2011. It specifies that
assert_type()uses equivalence, but type checkers are allowed to have an incomplete implementation that rejects some equivalent types. Discussion in https://discuss.python.org/t/specify-that-assert-type-checks-for-equivalence/92967Signoff: