When the input file contains GPyOpt, pip-compile fails: pip-compile fails on GPyOpt · Issue #2170 · jazzband/pip-tools · GitHub
The failure only occurs with Python-3.11, and not with Python-3.9
Nobody answered this bug in the pip-tools project, while pip-compile being an important part of the Python’s toolchain.
I need to convert one project from Python-3.9 to Python-3.11 and this bug prevents it because pip-compile is in the pipeline.
How can I find a workaround for this?
I see that gpyopt was last updated 5 years ago.
Maybe it needs a fix to work on python 3.11 and it is not pip at fault?
GPyOpt builds, installs, and runs fine with Python-3.11
I’ve ran several examples - they run successfully.
This suggests that something is wrong with pip-compile.
It looks like the error is coming from scipy, and possibly because the necessary build tools are not installed on the system. But in general it shouldn’t be necessary to build scipy, as long as you’re on a supported platform.
If you make a test project with just 3.11 and scipy, does pip-compile work?
Edit: is the error completely the same on Linux? I could imagine freebsd doesn’t have a wheel for 3.11…
I initially misdiagnosed the problem. The above problem exists on FreeBSD.
On Linux pip-compile fails in a very peculiar way. It fails on one particular reqs.in, but it succeeds when some blank lines are added.
I’ve wrote the bug description here: pip-compile fails on the requirements list without blank lines, and doesn't fail when some blank lines are added · Issue #2171 · jazzband/pip-tools · GitHub
pip-compile shouldn’t depend on blank lines, but it does.
This is with Python-3.11