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, Gobot1234, JelleZijlstra, gvanrossum, kj, med2277
Date 2022-02-14.16:34:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644856498.55.0.697704605397.issue46743@roundup.psfhosted.org>
In-reply-to
Content
> On the general class instanciation point would there be anything wrong with just adding a big red warning saying (on the non-existent) docs for these classes that they don't follow normal class initization or is this too insignificant of an issue to bother?

Which classes? Every class that inherits from Generic? That would be problematic -- we don't want the addition of typing information to change the behavior of a construct (or at least as little as possible).

> I think you could make this work with a Protocol as the bound TypeVar("T", bound=HasTheCorrectNewSignature)?

Sure.

But I am still inclined to reject the feature request as too obscure.
History
Date User Action Args
2022-02-14 16:34:58gvanrossumsetrecipients: + gvanrossum, JelleZijlstra, Gobot1234, kj, AlexWaygood, med2277
2022-02-14 16:34:58gvanrossumsetmessageid: <1644856498.55.0.697704605397.issue46743@roundup.psfhosted.org>
2022-02-14 16:34:58gvanrossumlinkissue46743 messages
2022-02-14 16:34:58gvanrossumcreate