Message217730
| Author | r.david.murray |
|---|---|
| Recipients | benjamin.peterson, exarkun, josh.r, r.david.murray |
| Date | 2014-05-01.21:47:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1398980851.59.0.595676086653.issue21408@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't think it's a bug. The subclass-goes-first behavior is very intentional. The implicit __ne__ returning the boolean inverse of __eq__ is what fooled me when I looked at it. Or did you mean that following the subclass rule in the case where object is the other class is possibly suspect? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-05-01 21:47:31 | r.david.murray | set | recipients: + r.david.murray, exarkun, benjamin.peterson, josh.r |
| 2014-05-01 21:47:31 | r.david.murray | set | messageid: <1398980851.59.0.595676086653.issue21408@psf.upfronthosting.co.za> |
| 2014-05-01 21:47:31 | r.david.murray | link | issue21408 messages |
| 2014-05-01 21:47:31 | r.david.murray | create | |