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 taleinat
Recipients epaine, gpolo, serhiy.storchaka, taleinat
Date 2020-09-26.13:22:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601126548.38.0.454874884795.issue41851@roundup.psfhosted.org>
In-reply-to
Content
As for an equal() method, I think that adding equal() which is different than the existing __eq__() would be a source of confusion. I also think using it wouldn't add anything, and would be less clear, compared to font1.actual() == font2.actual().

I'm definitely not happy with the existing __eq__() though, and think it would be worth discussing changing __eq__() to use self.actual() == other.actual() rather than just comparing names. That should be a separate issue, though - you're welcome to create one!
History
Date User Action Args
2020-09-26 13:22:28taleinatsetrecipients: + taleinat, gpolo, serhiy.storchaka, epaine
2020-09-26 13:22:28taleinatsetmessageid: <1601126548.38.0.454874884795.issue41851@roundup.psfhosted.org>
2020-09-26 13:22:28taleinatlinkissue41851 messages
2020-09-26 13:22:27taleinatcreate