As I look at Py_Initialize() further, I see some other 'features' that could be problematic when embedding: particularly the calls to Py_FatalError. An embedding application may be able to continue even if the Python interpreter cannot be initialized... certainly it should be up to the embedding application on how to handle the error, instead of having abort() called for it. It would also be nice if there were no calls fprintf and friends within the initialization path when doing embedded initialization. tree -- Tom Emerson Basis Technology Corp. Software Architect http://www.basistech.com "Beware the lollipop of mediocrity: lick it once and you suck forever"
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