[issue1533] Bug in range() function for large values

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Christian,

I was probably a bit sloppy using "range" instead of "xrange," but issue1540617 is limited to xrange only.  Are you still -10 on extending 
xrange on 64-bit platforms to +/- 2**63?  If so, what is your position 
on backporting py3k's unlimited range implementation?

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1533>
__________________________________