Quote:
Originally Posted by DiapDealer
Apologies. Disabling Sigil's update check does NOT prevent the embedded Python errors when launching Sigil in the normal Safe Mode. I will definitely be looking into this.
|
Somehow... xmlprocessor.py's call to import sigil_bs4 which is turn calling set_trace from the pdb module is picking up an asynchronous socket error when Windows Safe Mode's dead networking is encountered. The only problem is:
1) my python updatechecker is not to be run (via embedded python in main.cpp) when the SIGIL_SKIP_UPDATE_CHECK environment variable is set, and...
2) even if the environment variable is NOT set, the socket check in updatechecker.py is wrapped in a try/except clause so as to always return safe values.
So my question (to anyone--including myself!) is: How is a process started via xmlprocesser.py and BeautifulSoup picking up an error from Windows about a dead network when no network check is supposed to be taking place (and even if it were; precautions are in place to prevent crashes and always return safe values)?
Yes. My brain just broke.