Message336234
| Author | remi.lapeyre |
|---|---|
| Recipients | Eric Appelt, docs@python, mark.dickinson, ncoghlan, remi.lapeyre, serhiy.storchaka, xtreak |
| Date | 2019-02-21.16:10:40 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1550765440.46.0.572272827082.issue33039@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Yes it is. Thanks for finding that @Serhiy. Since nobody objected to the change on the mailing list and people seem to agree in issue 20092: [R. David Murray] 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. I will post my patch tonight. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-02-21 16:10:40 | remi.lapeyre | set | recipients: + remi.lapeyre, mark.dickinson, ncoghlan, docs@python, serhiy.storchaka, Eric Appelt, xtreak |
| 2019-02-21 16:10:40 | remi.lapeyre | set | messageid: <1550765440.46.0.572272827082.issue33039@roundup.psfhosted.org> |
| 2019-02-21 16:10:40 | remi.lapeyre | link | issue33039 messages |
| 2019-02-21 16:10:40 | remi.lapeyre | create | |