[Neal Norwitz] > The original problem was actually 1e9. Which is about maxint/2, which I checked in. > The test is somewhat dubious, so anything to reduce the problems > would be good. Perhaps the test should just be removed? So long as it's testing Python's overflow-checking code instead of the platform realloc(), it should be fine. It's probably still dubious on Win64 (where sys.maxint is still 2**31-1), but should be fine everywhere else). I'll worry about Win64 when somebody runs it <1/64 wink>.
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