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 Zac Hatfield-Dodds
Recipients BTaskaya, Zac Hatfield-Dodds, corona10, gvanrossum, kj, levkivskyi, serhiy.storchaka
Date 2020-11-16.05:08:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> @Hatfield-Dodds, if we changed typing.Callable to return ((int, int), str) but continued to return ([int, int], str), would that suffice for your purposes?

For performance reasons I'd prefer that the return value be hashable for both, but we've already shipped the workarounds [0,1,2] for 3.9.0 and will maintain that until 3.9 reaches EOL in any case.

Whether we return (int, int, str) or ((int, int), str) doesn't make much difference to me, the latter will require a trivial patch to [2] so please do whatever makes most sense upstream.

> Also, maybe we should make builtins.callable generic as well?

I like this idea :-)

Date User Action Args
2020-11-16 05:08:07Zac Hatfield-Doddssetrecipients: + Zac Hatfield-Dodds, gvanrossum, serhiy.storchaka, levkivskyi, corona10, BTaskaya, kj
2020-11-16 05:08:07Zac Hatfield-Doddssetmessageid: <>
2020-11-16 05:08:07Zac Hatfield-Doddslinkissue42195 messages
2020-11-16 05:08:07Zac Hatfield-Doddscreate