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.
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) | Date: 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) | Date: 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. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:56:34 | admin | set | github: 47183 |
| 2008年05月21日 13:23:44 | ncoghlan | set | status: open -> closed resolution: not a bug messages: + msg67153 |
| 2008年05月21日 13:19:21 | ncoghlan | create | |