➜

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.

classification
标题: set() comparisons do not play well with others
类型: Stage:
Components: Versions:
process
状态: closed Resolution: not a bug
Dependencies: 后续:
分配给: 抄送列表: ncoghlan
优先级: normal 关键字:

Created on 2008-05-21 13:19 by ncoghlan, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg67152 - (view) Author: Alyssa Coghlan (ncoghlan) * (Python committer) 日期: 2008-05-21 13:19
The rich compare implementation for set objects raises TypeError
directly instead of returning NotImplemented to allow the other type
involved in the comparison a chance at handling the operation.
msg67153 - (view) Author: Alyssa Coghlan (ncoghlan) * (Python committer) 日期: 2008-05-21 13:23
Eh, never mind, raising the TypeError explicitly is necessary due to the
misbehaviour of the default comparisons in 2.x.

I'll work around the problem in my test case.
历史
日期 用户 动作 参数
2022-04-11 14:56:34admin修改github: 47183
2008-05-21 13:23:44ncoghlan修改状态: open -> closed
resolution: not a bug
消息: + msg67153
2008-05-21 13:19:21ncoghlan创建