Closed gregrebholz closed 6 years ago
I've traced this to the use of --install-option="--prefix=/install" ... perhaps hexbytes is not relocatable?
I've traced this to the use of --install-option="--prefix=/install" ... perhaps hexbytes is not relocatable?
It's possible. I've never used that option, so haven't done anything special to support it. Are you interested in contributing?
Looking to add support, I've learned that passing "--prefix=/install" to setup.py is no longer preferred in Python; passing "--target=/install" to pip itself is the modern approach. There are many caveats regarding binaries, libraries, scripts and data and how they react differently to the many related options, but "pip install --target=/install hexbytes" works just fine for me, so I'll close this. Further reading for posterity:
Similar to issue #3 I am getting this stack trace when installing via pip (including when hexbytes is a dependency of other packages), but I am using python3/pip3 --
This was in a Docker container built on library:python:latest which is ubuntu at the lowest layer, but also occurs on library:python:3.6-alpine for Alpine Linux, and even another user's Alpine based docker image "frolvlad/alpine-python3". In the error above I'm running
pip 18.0 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
but I've also see it from pip 10.0.1 from python3.6. The Dockerfile is:And the build then is simply:
sudo docker build --no-cache -t script .
which failed on the pip run.I've tried installing pandoc with
apt-get update -y && apt install -y pandoc
in case there was a version dependency there.I ran into this while trying to install "web3" with my initial requirements.txt as the one line:
web3>=4.4.1,<5
... but I'm now troubleshooting with justhexbytes<1.0.0,>=0.1.0
. Thanks for any help you can provide.