[issue2934] set() comparisons do not play well with others

2008-05-21 Thread Nick Coghlan
Nick Coghlan <[EMAIL PROTECTED]> added the comment: 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. -- resolution: -> invalid status: open -> closed _

[issue2934] set() comparisons do not play well with others

2008-05-21 Thread Nick Coghlan
New submission from Nick Coghlan <[EMAIL PROTECTED]>: 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. -- messages: 67152 nosy: ncoghlan sev