Recently, various discussions about builtin range have come up in the tracker that need to be brought to the attention of the general developer pool:
First of all, should the length of range be completely constricted by Py_ssize_t? (issue 2690) Since indexing already is constrained by this, it would make sense to make the whole object live under that law. However, it appears Amaury has a patch to allow these huge ranges [1] Also, how should range values be normalized in the constructor (if at all) to make ranges over the same set of integers equivalent? (see 2603) For example, given the set of integers [0, 2, 4], which should happen: >>> range(0, 5, 2) range(0, 6, 2) >>> range(0, 6, 2) range(0, 6, 2) or >>> range(0, 5, 2) range(0, 5, 2) >>> range(0, 6, 2) range(0, 6, 2) [ I probably missed something, so feel free to add it. ] [1] http://bugs.python.org/msg65807 -- Cheers, Benjamin Peterson _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
