Steve Dower added the comment: I've been meaning to get to looking at this issue for a couple of days now, sorry.
There are two critical pieces here: * don't delete or move _socket.pyd * don't delete or move python36._pth (but possibly update it) The first one should be obvious - I assume you haven't messed that bit up :) The second one is the "static" way of setting sys.path, as Zach suggests. By default, it should include 'python36.zip' and '.', which is the directory containing python36._pth and python36.dll. If you move any of these around, sys.path will be automatically inferred, which could break things. Further, if you move/remove python36._pth, the registry and environment will be used to locate files rather than only looking in the application directory. This may be bad. One final tip - you can rename python36._pth to your_exe_name._pth if you want, and if you are embedding then you can get roughly equivalent behaviour using PySys_SetPath. If none of this works, we'll need you to provide some information about your application, especially the code used to initialize the interpreter, import socket, and the layout of all the files in your app. (Right now, you're asking us to guess basically every detail that is relevant to the bug, hence we're replying with "read the docs" and "try everything" rather than a specific fix ;) ) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30446> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
