The latest nlopt always builds the python extension, even when the python use flag is disabled. Also it builds it against the currently active python interpreter, not against the one set in PYTHON_TARGETS. I have successful builds against python3.6 and python3.8 (did not test the functionality, but build succeeds). Reproducible: Always Steps to Reproduce: 1. USE=-python emerge -1 sci-libs/nlopt 2. qlist nlopt Actual Results: [snip] /usr/lib/python3.8/site-packages/nlopt.py /usr/lib/python3.8/site-packages/__pycache__/nlopt.cpython-38.pyc /usr/lib/python3.8/site-packages/__pycache__/nlopt.cpython-38.opt-1.pyc /usr/lib/python3.8/site-packages/__pycache__/nlopt.cpython-38.opt-2.pyc /usr/lib/python3.8/site-packages/_nlopt.la /usr/lib/python3.8/site-packages/_nlopt.so.0.8.2 /usr/lib/python3.8/site-packages/_nlopt.so /usr/lib/python3.8/site-packages/_nlopt.so.0 Expected Results: No python extension should be built.
I think both issues are fixed in the current nlopt-2.6.2-r1.ebuild. Please let us know if you run into them again.