On Thu, 2020-06-11 at 12:55 +0200, chrysn wrote:
> Package: python3-pip
> Version: 20.1.1-2
> Severity: normal
>
> In pypy3 venvs, installing the cryptography package fails. As replacing
> pip with the upstream pip makes things work, and because the whole
> situation looks similar to #955414 / #954256 (where I found the
> workaround), there is reason to assume this is relating to Debian
> customizations in pip.
I just ran into this issue as well and agree with the similarities to
the bugs you mentioned. On my system it appears to be unrelated to the
cryptography package and can be reproduced using the same steps as in
#954256:
pypy3 -m venv /tmp/venv/
source /tmp/venv/bin/activate
mkdir /tmp/pypa
cd /tmp/pypa
echo "from setuptools import setup; setup()" > setup.py
touch pyproject.toml
pip install --isolated -e .
Which fails with:
Obtaining file:///tmp/pypa
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'error'
ERROR: Command errored out with exit status 1:
command: /tmp/venv/bin/pypy3-c
/usr/share/python-wheels/pep517-0.8.2-py2.py3-none-any.whl/pep517/_in_process.py
get_requires_for_build_wheel /tmp/tmpu8qlrd77
cwd: /tmp/pypa
Complete output (1 lines):
/tmp/venv/bin/pypy3-c: can't find '__main__' module in
'/usr/share/python-wheels/pep517-0.8.2-py2.py3-none-any.whl/pep517/_in_process.py'
----------------------------------------
ERROR: Command errored out with exit status 1: /tmp/venv/bin/pypy3-c
/usr/share/python-wheels/pep517-0.8.2-py2.py3-none-any.whl/pep517/_in_process.py
get_requires_for_build_wheel /tmp/tmpu8qlrd77 Check the logs for full command
output.
As you noted, and as in #954256, running `pip install --force pip` in
the venv avoids the error.
Thanks,
Kevin
