➜

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 ElizabethU
Recipients ElizabethU, cjw296, iritkatriel, mariocj89, michael.foord, p-ganssle, serhiy.storchaka, xtreak
Date 2020-10-17.21:57:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602971825.46.0.0209392129476.issue37555@roundup.psfhosted.org>
In-reply-to
Content 
I believe it should work in both 3.8 and 3.9, the difference is that someone (Serhiy if I'm remembering correctly?) did the work in 3.9 of standardizing which side of the = the needle was on. So, this change works on 3.9 without the _AnyComparer class I added, but I believe unless _AnyComparer has been removed, this change would work in 3.8. Xtreak, it seems like most of your concerns about backporting it are about how complicated this part of the code is, and wanting it to get more testing via the mock backport? Is there any way I can help mitigate those concerns, or keep up with how much use it's gotten from the mock backport so we can determine when (if ever) it would be a good time to backport this?
History
Date User Action Args
2020-10-17 21:57:05ElizabethUsetrecipients: + ElizabethU, cjw296, michael.foord, serhiy.storchaka, p-ganssle, mariocj89, xtreak, iritkatriel
2020-10-17 21:57:05ElizabethUsetmessageid: <1602971825.46.0.0209392129476.issue37555@roundup.psfhosted.org>
2020-10-17 21:57:05ElizabethUlinkissue37555 messages
2020-10-17 21:57:05ElizabethUcreate