[Python-Dev] xrange vs. int.__getslice__
Vladimir 'Yu' Stepanov
vys at renet.ru
Tue Jun 13 09:34:12 CEST 2006
More information about the Python-Dev mailing list
Tue Jun 13 09:34:12 CEST 2006
- Previous message: [Python-Dev] [Python-checkins] r46795 - in python/trunk: Doc/lib/libstdtypes.tex Lib/test/string_tests.py Misc/NEWS Objects/stringobject.c Objects/unicodeobject.c
- Next message: [Python-Dev] xrange vs. int.__getslice__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You were bothered yet with function xrange ? :) I suggest to replace it.
---------------------------------------------
for i in xrange(100): pass
vs.
for i in int[:100]: pass
---------------------------------------------
---------------------------------------------
for i in xrange(1000, 1020): pass
vs.
for i in int[1000:1020]: pass
---------------------------------------------
---------------------------------------------
for i in xrange(200, 100, -2): pass
vs.
for i in int[200:100:-2]: pass
---------------------------------------------
- Previous message: [Python-Dev] [Python-checkins] r46795 - in python/trunk: Doc/lib/libstdtypes.tex Lib/test/string_tests.py Misc/NEWS Objects/stringobject.c Objects/unicodeobject.c
- Next message: [Python-Dev] xrange vs. int.__getslice__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list