Travis E. Oliphant wrote: > Sounds wonderful. Would love to see this in Python 2.5. This will fix > important 64-bit issues. Perhaps someone could explain to me what the > difference between Py_ssize_t and Py_intptr_t would be? Is this not a > satisfactory Py_ssize_t already? Practically, yes. Conceptually, intptr_t and size_t are different things: sizeof(void*) might differ from sizeof(size_t) (e.g. when you have segment and offset in pointers). I believe in flat-address space machines, they are always the same. Regards, Martin
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