Message 378353 - 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	BTaskaya, emma_smith, glyph, gvanrossum
Date	2020-10-09.21:27:20
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
This behavior (only relevant with `from __future__ import annotations`) has been around since @singledispatchmethod was introduced in 3.8, so I agree we should treat it as a feature request. In the meantime, maybe a workaround is to move the register call out of the class? It looks a little bit ugly but probably works. (Disclaimer: I'm not familiar with singledispatchmethod.)

This behavior (only relevant with `from __future__ import annotations`) has been around since @singledispatchmethod was introduced in 3.8, so I agree we should treat it as a feature request.

In the meantime, maybe a workaround is to move the register call out of the class? It looks a little bit ugly but probably works.

(Disclaimer: I'm not familiar with singledispatchmethod.)

History
Date	User	Action	Args
2020-10-09 21:27:20	gvanrossum	set	recipients: + gvanrossum, glyph, emma_smith, BTaskaya
2020-10-09 21:27:20	gvanrossum	set	messageid: <[email protected]>
2020-10-09 21:27:20	gvanrossum	link	issue41987 messages
2020-10-09 21:27:20	gvanrossum	create