Message185532
| Author |
barry |
| Recipients |
alex, barry, docs@python, eric.snow |
| Date |
2013年03月30日.00:39:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20130329203938.6a53389b@limelight.wooz.org> |
| In-reply-to |
<1364603376.41.0.418321948666.issue17576@psf.upfronthosting.co.za> |
| Content |
On Mar 30, 2013, at 12:29 AM, Eric Snow wrote:
>Would it be okay to do a check on __index__ after the PyLong_Check()
>succeeds? Something like this:
>
> if (PyLong_Check(item) &&
> item->ob_type->tp_as_number->nb_index == PyLong_Type.tp_as_number->nb_index) {
> Py_INCREF(item);
> return item;
> }
>
>This is something Nick and I were talking about at the sprints regarding fast
>paths in the abstract API (for mappings and sequences in our case).
I think that would work, yes. With this extra check, overriding __index__()
in the subclass should fail this condition and fall back to the
PyIndex_Check() clause. |
|