➜

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 terry.reedy
Recipients Juraj.Variny, bethard, chris.jerdonek, docs@python, ezio.melotti, r.david.murray, terry.reedy
Date 2012-11-11.19:55:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352663705.72.0.543471051014.issue16418@psf.upfronthosting.co.za>
In-reply-to
Content 
I am arguing that (x)range *should* be usable for large numbers of options *because* the containment test is O(1). What happens is you *do* use xrange instead of range in 2.7 or 3.x instead of 2.7?

In 2.x, range(n) *is* a list so that is a bad choice for large n, regardless of the display issue, which could be fixed separately as is being done on other issues.
History
Date User Action Args
2012-11-11 19:55:05terry.reedysetrecipients: + terry.reedy, bethard, ezio.melotti, r.david.murray, chris.jerdonek, docs@python, Juraj.Variny
2012-11-11 19:55:05terry.reedysetmessageid: <1352663705.72.0.543471051014.issue16418@psf.upfronthosting.co.za>
2012-11-11 19:55:05terry.reedylinkissue16418 messages
2012-11-11 19:55:05terry.reedycreate