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 kj
Recipients AlexWaygood, andreash, gvanrossum, kj, kumaraditya, python-dev
Date 2022-01-12.14:04:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641996265.15.0.00867139545282.issue46333@roundup.psfhosted.org>
In-reply-to
Content
@Andreas
First of all, thanks for addressing my questions on the PR. I have one more question which I'll post here since it's not entirely related to your PR.

ForwardRef isn't meant to be explicitly instantiated by a user [1] (it's a typing internal class), so do you mind sharing what your current use case is please? My concern here is that exposing things in __repr__ would force us to keep `module` forever (I'm 100% fine with __eq__ and __hash__). After digging up the commit history, I now recall that the module parameter was used solely as a fix for ForwardRefs in different-module TypedDict (see GH-27017 or bpo-41249). It's not used anywhere else, so I don't know if your current use case was ever intended when the module parameter was added.

[1]: https://docs.python.org/3/library/typing.html#typing.ForwardRef
History
Date User Action Args
2022-01-12 14:04:25kjsetrecipients: + kj, gvanrossum, python-dev, kumaraditya, AlexWaygood, andreash
2022-01-12 14:04:25kjsetmessageid: <1641996265.15.0.00867139545282.issue46333@roundup.psfhosted.org>
2022-01-12 14:04:25kjlinkissue46333 messages
2022-01-12 14:04:24kjcreate