get_origin gives inconsistent results for differently defined Unions about typing_inspect HOT 3 OPEN

Yes, I think it is a bug. We support X | Y syntax in is_union_type(). I am not sure what the value get_origin() should return (probably we should match typing behavior), but definitely not None.

from typing_inspect.

We support X | Y syntax in is_union_type()

Thanks for the tip. I guess this will work for me.

I am not sure what the value get_origin() should return

From the docs: Union type; Union[X, Y] is equivalent to X | Y .. so they should behave the same, or?

probably we should match typing behavior

Also a good idea. But maybe (just maybe) upstream is wrong :)

from typing_inspect.

In Python 3.13 we may well merge types.UnionType and typing.Union: python/cpython#105499. But in earlier Python versions we're not going to change the upstream behavior.

I would recommend typing-inspect to match the behavior of typing.get_origin, so get_origin(int | str) is types.UnionType and get_origin(Union[int, str]) is typing.Union.

from typing_inspect.