Thomas Stevenson added the comment:
Thank you Steve and Zachary. The context you provided helped me track it down,
so I have marked this closed. In case it benefits anyone in future as well, I
ran into a subsequent topic where the C++ app was compiled in debug and hence
the actual file
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
Zachary Ware added the comment:
I suspect you'll need to set sys.path (PySys_SetPath, I think, but trust the
docs more than me). Try importing sys and printing sys.path to confirm.
--
___
Python tracker
New submission from Thomas Stevenson:
Trying to import the socket module using the embedded distribution for 3.6.1, I
get the error: : No module named '_socket'
Running with the standard interpreter works:
Python 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 17:54:52) [MSC v.1900 32 bit (Intel)]
on