diff options
| author | Tim Peters <tim.peters@gmail.com> | 2004-08-08 07:17:39 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2004-08-08 07:17:39 (GMT) |
| commit | feec4533e21a612e9a5b665c27b1a3eb84e04bb3 (patch) | |
| tree | e721c83b44443f2cbda66a7acab7ddd4cd30a9d6 /Misc | |
| parent | d976ab7caf098eecf44173bbce8101f13ce79d86 (diff) | |
| download | cpython-feec4533e21a612e9a5b665c27b1a3eb84e04bb3.zip cpython-feec4533e21a612e9a5b665c27b1a3eb84e04bb3.tar.gz cpython-feec4533e21a612e9a5b665c27b1a3eb84e04bb3.tar.bz2 | |
Bug 1003935: xrange overflows
Added XXX comment about why the undocumented PyRange_New() API function
is too broken to be worth the considerable pain of repairing.
Changed range_new() to stop using PyRange_New(). This fixes a variety
of bogus errors. Nothing in the core uses PyRange_New() now.
Documented that xrange() is intended to be simple and fast, and that
CPython restricts its arguments, and length of its result sequence, to
native C longs.
Added some tests that failed before the patch, and repaired a test that
relied on a bogus OverflowError getting raised.
Diffstat (limited to 'Misc')
0 files changed, 0 insertions, 0 deletions