Joseph Thomson <joseph.thom...@gmail.com> added the comment: Seeing as the range type has most likely stabalised by now, I would like to renew this issue. The current behaviour of range/xrange could introduce unforeseen performance issues if users are not aware of its inner workings.
Also, as I said in my closed duplicate issue, 'if value in range(lower, upper)' to me looks far more Pythonic than 'if value >= lower and value < upper'. Although this may be a minor point, I think it is noteworthy. As for the prospect of producing a patch myself, I have checked out and taken a look at the code, but it is somewhat alien to me, and I thought it'd probably be more sensible to leave it to the people who know what they're doing. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1766304> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
