Closed musicinmybrain closed 3 months ago
This is very similar to https://github.com/agronholm/typeguard/issues/443, but it seems to be specific to Python 3.13, and occurs in a release that already contains d481a51dd4cb347621b99e144f935e0848977f6e.
Yep, I'm aware of this, and I think this is caused by typing_extensions
not yet supporting Python 3.13. Typeguard relies on typing_extensions.is_typeddict()
to recognize typed dicts from both that library and the standard library.
Thanks for the response. If the problem is in typing_extensions
, I wonder if they know about it. Release 4.11.0 advertises Python 3.13.0a5 compatibility, and Python 3.13 appears to be in their test matrix.
I need to thoroughly check this before filing any issue with them.
Ok! No big hurry – I’ll track this issue. Thanks for looking into it, and please let me know if there’s anything I can do.
It looks like they're no longer using typing.TypedDict
as typing_extensions.TypedDict
, so I need to change the dependencies again.
Yeah, this is definitely fixable on my side, but I need a good night's rest to wrap my head around the solution.
This was fixed via #460.
Things to check first
[X] I have searched the existing issues and didn't find my bug already reported there
[X] I have checked that my bug is still present in the latest release
Typeguard version
4.2.1
Python version
3.13.0a5
What happened?
How can we reproduce the bug?