Message92188
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. |
|
Date |
User |
Action |
Args |
2009-09-02 21:47:13 | hpesoj | set | recipients:
+ hpesoj, rhettinger, mark.dickinson, belopolsky, pitrou, stargaming |
2009-09-02 21:47:13 | hpesoj | set | messageid: <1251928033.27.0.432724191711.issue1766304@psf.upfronthosting.co.za> |
2009-09-02 21:47:11 | hpesoj | link | issue1766304 messages |
2009-09-02 21:47:11 | hpesoj | create | |
|