You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to get Bottleneck to build from master using Python3.10 in the GitHub Actions environment. After finding the deadsnakes python action for installing the python-dev headers in Ubuntu 20.04 (https://github.com/deadsnakes/action), I was still having issues with the builds failing (despite everything working fine locally).
The fix to this issue raised here was actually solved by my colleague @aulemahal in another issue. I am opening this issue for context, with a PR incoming.
Explanation:
I believe I have found the source of the error, at least in my configuration. It is due to the specific of virtual environment creation with python -m venv.
When creating a virtual environment with venv into ${venv}, a ${venv}/include folder is created and sys.prefix == ${venv}. However, in opposition to virtualenv, the include folder is empty, it exists solely for files created by packages installed within the environment. Source : PEP 405.
The include folders needed by bottleneck are still accessible, but their path has to be constructed relative to sys.base_prefix instead, to get the system files. Changing:
I have been trying to get Bottleneck to build from master using Python3.10 in the GitHub Actions environment. After finding the deadsnakes python action for installing the python-dev headers in Ubuntu 20.04 (https://github.com/deadsnakes/action), I was still having issues with the builds failing (despite everything working fine locally).
The fix to this issue raised here was actually solved by my colleague @aulemahal in another issue. I am opening this issue for context, with a PR incoming.
Explanation:
I believe I have found the source of the error, at least in my configuration. It is due to the specific of virtual environment creation with
python -m venv
.When creating a virtual environment with
venv
into${venv}
, a${venv}/include
folder is created andsys.prefix == ${venv}
. However, in opposition tovirtualenv
, the include folder is empty, it exists solely for files created by packages installed within the environment. Source : PEP 405.The include folders needed by bottleneck are still accessible, but their path has to be constructed relative to
sys.base_prefix
instead, to get the system files. Changing:bottleneck/bottleneck/src/bn_config.py
Line 30 in f2bc792
to
fixes the problem.
Of course, I have
pythonX.X-dev
installed (on ubuntu) for this to work.EDIT: I have python 3.7.9.
Originally posted by @aulemahal in #348 (comment)
The text was updated successfully, but these errors were encountered: