➜

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 sobolevn
Recipients gvanrossum, kj, sobolevn
Date 2021-12-23.09:50:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1640253025.77.0.520385746674.issue46162@roundup.psfhosted.org>
In-reply-to
Content 
Original discussion in `typing` bug tracker: https://github.com/python/typing/issues/985

Short description:
- `property[GetType, SetType]` is required for us to remove a lot of special casing from type-checkers and just use the primitive type
- In runtime it copies the same behavior `list` / `dict` / other primitive types have under PEP585

Open questions:
- I think that it is too late to backport this in 3.10. Am I right?
- I hope that `from __future__ import annotations` will just work for this new change. Is there anything I should do in scope of this PR? Is my assumption about `__future__` import is even correct in this context? Do I need to test that it works with `__future__ annotations`?
History
Date User Action Args
2021-12-23 09:50:25sobolevnsetrecipients: + sobolevn, gvanrossum, kj
2021-12-23 09:50:25sobolevnsetmessageid: <1640253025.77.0.520385746674.issue46162@roundup.psfhosted.org>
2021-12-23 09:50:25sobolevnlinkissue46162 messages
2021-12-23 09:50:25sobolevncreate