Message 413362 - Python tracker

➜

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	AlexWaygood, JelleZijlstra, docs@python, gvanrossum, kj, sobolevn
Date	2022-02-16.21:53:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1645048398.88.0.626594595692.issue46769@roundup.psfhosted.org>
In-reply-to

Content
Maybe historically constrained type vars predated bound type vars. This could have influenced the way PEP 484 was written and then the docs were derived from the PEP. But yes, this should be fixed in as many places as possible (including the mypy docs, probably). I would even support a minor update to PEP 484 to help people find the right way (the PEP is still widely cited). It would have to be just be a textual change, not a spec change.

Maybe historically constrained type vars predated bound type vars. This could have influenced the way PEP 484 was written and then the docs were derived from the PEP.

But yes, this should be fixed in as many places as possible (including the mypy docs, probably).

I would even support a minor update to PEP 484 to help people find the right way (the PEP is still widely cited). It would have to be just be a textual change, not a spec change.

History
Date	User	Action	Args
2022-02-16 21:53:18	gvanrossum	set	recipients: + gvanrossum, docs@python, JelleZijlstra, sobolevn, kj, AlexWaygood
2022-02-16 21:53:18	gvanrossum	set	messageid: <1645048398.88.0.626594595692.issue46769@roundup.psfhosted.org>
2022-02-16 21:53:18	gvanrossum	link	issue46769 messages
2022-02-16 21:53:18	gvanrossum	create