Message207072
| Author | r.david.murray |
|---|---|
| Recipients | Arfrever, benjamin.peterson, ethan.furman, r.david.murray |
| Date | 2013-12-29.13:44:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1388324645.35.0.945276548175.issue20092@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Ah, I see. A link to that issue would have been helpful :). To summarize for anyone like me who didn't follow that issue: __index__ means the object can be losslessly converted to an int (is a true int), while __int__ may be an approximate conversion. Thus it makes sense for an object to have an __int__ but not __index__, but vice-versa does not make sense. Is someone updating the docs to reflect this, or should that be spun off as a separate issue as well? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-12-29 13:44:05 | r.david.murray | set | recipients: + r.david.murray, benjamin.peterson, Arfrever, ethan.furman |
| 2013-12-29 13:44:05 | r.david.murray | set | messageid: <1388324645.35.0.945276548175.issue20092@psf.upfronthosting.co.za> |
| 2013-12-29 13:44:05 | r.david.murray | link | issue20092 messages |
| 2013-12-29 13:44:04 | r.david.murray | create | |