This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients BTaskaya, barry, brett.cannon, eric.smith, gvanrossum, levkivskyi, lukasz.langa, vstinner
Date 2020-05-26.22:18:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
- Double forward ref: IMO this can be resolved in the get_type_hints() functions. (Łukasz do you agree?)

- inspect.signature(): Maybe this could switch to using typing.get_type_hints()? Then again if performance is important here maybe we cannot change anything.

- dataclasses hacks: these should just be resolved.

Another thought: maybe some of these issues can be considered bugs in 3.9 as well, and we should fix them there too? That might help us decide the right path forward. After all we should really encourage people to start using `from __future__ import annotations` in their code, to help them get ready for these issues in 3.10.

Final thought: I know at least the Dropbox client team, and possibly also Instagram, has already turned on `from __future__ import annotations` by default in their local fork of Python. Maybe we can ask them if they ever felt the need to change inspect.signature or typing.get_type_hints.
Date User Action Args
2020-05-26 22:18:57gvanrossumsetrecipients: + gvanrossum, barry, brett.cannon, vstinner, eric.smith, lukasz.langa, levkivskyi, BTaskaya
2020-05-26 22:18:57gvanrossumsetmessageid: <>
2020-05-26 22:18:57gvanrossumlinkissue38605 messages
2020-05-26 22:18:56gvanrossumcreate