> I may well be barking up the wrong tree here, but as a first guess > it looks as though something in the _PySys_Init function in > Python/sysmodule.c is (directly or indirectly) causing the > OverflowError to be raised. My theory would be different. There is a pending unchecked OverflowError before the import, and the err-occurred check after the import picks it up. Of course, your guess is as good as mine. While barking up trees: My guess is that it's a compiler bug (i.e. the compiler generating bad code). 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