> ISTM, the use of 64-bit builds is growing in popularity. It was be a bummer > to have a locked-in an effective size limit for dictionaries and sets > because the API only supports 32-bit hash values. If the ABI is frozen with 3.2, it would still be possible to introduce "wide" hashes - it just will have to be a compatible change. > The thread seems to show agreement that the hash values should be > Py_ssize_t but the chance to fix it will be lost unless core devs get > more time to work on the problem or unless the ABI freeze is deferred. I agree in principle, also, but would like to see some analysis on existing third-party modules. 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