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 mark.dickinson
Recipients eric.smith, kszawala, mark.dickinson
Date 2009-09-24.11:36:00
SpamBayes Score 0.006866882
Marked as misclassified No
Message-id <1253792162.11.0.510010328214.issue6985@psf.upfronthosting.co.za>
In-reply-to
Content
Mark]
> I *think* range uses long internally

Aargh!  Sorry, Eric.  I take it back.  *xrange* uses longs internally
(and used to use ints once upon a time, IIRC), but there's a weird mix
of int and long in builtin_range that doesn't make any sense to me.  I
suspect it's historical, and may have to do both with the xrange
int->long switch and the int -> Py_ssize_t switch.
History
Date User Action Args
2009-09-24 11:36:02mark.dickinsonsetrecipients: + mark.dickinson, eric.smith, kszawala
2009-09-24 11:36:02mark.dickinsonsetmessageid: <1253792162.11.0.510010328214.issue6985@psf.upfronthosting.co.za>
2009-09-24 11:36:01mark.dickinsonlinkissue6985 messages
2009-09-24 11:36:00mark.dickinsoncreate