This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author AlokSinghal
Recipients AlokSinghal, rhettinger, terry.reedy, thomasguest
Date 2014-04-21.23:11:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398121885.88.0.261982541663.issue6305@psf.upfronthosting.co.za>
In-reply-to
Content
This updated patch has support for starting in fast mode until the next count would result in overflow in Py_ssize_t.  The first patch started in slow mode as soon as any of 'start', 'stop', or 'step' was outside of the range.  With this patch, we start in fast mode if possible and then transition to slow mode when needed.

I also tested this patch for correctness for the following cases:

- starting in slow mode,
- transition from fast -> slow,
- pickle/unpickle

I did this by temporarily changing the code twice:

- to always use fast mode, and
- pretending that overflow occurs at value 5 instead of PY_SSIZE_T_MAX.
History
Date User Action Args
2014-04-21 23:11:25AlokSinghalsetrecipients: + AlokSinghal, rhettinger, terry.reedy, thomasguest
2014-04-21 23:11:25AlokSinghalsetmessageid: <1398121885.88.0.261982541663.issue6305@psf.upfronthosting.co.za>
2014-04-21 23:11:25AlokSinghallinkissue6305 messages
2014-04-21 23:11:25AlokSinghalcreate