But it turns out that neither /usr/local/lib is in lib search path nor is /usr/include in include search path by default. Arguably this is somebody else's bug, but it's inconvenient.
The workaround is to download the repo yourself and specify manually with build_ext:
I've noticed that installs are particularly finicky on OSX.
Suppose this configuration:
There's not a good way to install nanomsg-python from pip. For example you might naively try
But it turns out that neither /usr/local/lib is in lib search path nor is /usr/include in include search path by default. Arguably this is somebody else's bug, but it's inconvenient.
The workaround is to download the repo yourself and specify manually with build_ext:
But for requirements.txt or other pip install, this is very unsatisfactory.
Finally, using
python3 setup.py develop
in lieu ofpython3 setup.py install
is inexplicably broken; it installs without error but it fails to import.I'm not totally sure what is afoot here, but I've seen this behavior on 2 systems now and so it may be worth investigating