Nice investigative work, kudos! On Mon, 7 Mar 2016, Bernard GODARD wrote:
The configure script is actually determining first if it should use the module sysconfig or the module distutils.sysconfig depending on python version and platform. For version 3 it uses the former.
I think that using the `sysconfig` module instead of `distutils.sysconfig` is the correct and recommended approach by Python developers for the following versions of Python: 2.7+ and 3.2+. So it looks like if `AM_PATH_PYTHON` is doing the right thing...
This gives an incorrect location.
These modules are supposed to be patched by Debian and Ubuntu maintainers to return the correct distro-specific location, so if this is not the case, then the patches are not complete and/or correct.
I have edited the configure script to always choose distutils.sysconfig. However this gives /usr/local/lib/python3/dist-packages whereas sys.path contains /usr/local/lib/python3.5/dist-packages. I have added a symlink from/usr/local/lib/python3 to /usr/local/lib/python3.5
This definitively sounds fishy... Would you care enough to open an issue with Debian people about that? If yes, please post the link here, I'd be curious about what they have to say; if this is a genuine issue, then it must be basically affecting the whole Python 3 world in Debian / Ubuntu.
What a mess. I will consider virtualenv next time.
Now maybe you can see why I'm still not thrilled by this idea to go for the split? ;-) This has caused me personally as an upstream years of pain, and I can't really say it made much good to the users, because the creative ones still find means to hose their system either way.
-- Sincerely yours, Yury V. Zaytsev _______________________________________________ NLopt-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
