➜
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.
Created on 2009-09-02 20:49 by hpesoj, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| range.py | hpesoj, 2009-09-02 20:49 | Improved range demo script | ||
| Messages (2) | |||
|---|---|---|---|
| msg92183 - (view) | Author: Joseph Thomson (hpesoj) | Date: 2009-09-02 20:49 | |
The range type should implement the __contains__ method. Currently an expression like 'x in range(10000000)' will iterate through every item in the range (exiting when an item tests true for equality); this is highly unnecessary as the following expression will perform the same function in a fraction of the time: value >= start and value < stop and (value - start) % step == 0 The biggest advantage of this modification would be to allow users to say: if foo in range(lower, upper): bar() instead of: if foo >= lower and foo < upper: bar() safe in the knowledge that they are losing no performance. The former is also far more Pythonic in my opinion :). If there is still any doubt (which I doubt), I have attached an example script showing what is to be gained. |
|||
| msg92184 - (view) | Author: Mark Dickinson (mark.dickinson) *  |
Date: 2009-09-02 21:09 | |
Closing this as a duplicate of issue 1766304. Joseph, please could you renew the discussion in that issue instead? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:52 | admin | set | github: 51075 |
| 2009-09-02 21:09:58 | mark.dickinson | set | status: open -> closed nosy: + mark.dickinson messages: + msg92184 superseder: improve xrange.__contains__ resolution: duplicate |
| 2009-09-02 20:49:19 | hpesoj | create | |