The range object is currently defined in Objects/rangeobject.c as typedef struct { PyObject_HEAD long start; long step; long len; } rangeobject; Is this consistent with PEP 353, or should Py_ssize_t be used instead of long? It looks like some of the code in rangeobject.c is already Py_ssize_t aware (see range_item and range_length), but it assumes that it is safe to cast long to ssize_t and back.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4