Closed cooperlees closed 1 year ago
Can you reduce the example to the install of the single package that's failing? I can't work out from your output what's happening. I have a suspicion that this might be related to something using setup_requires
, but your example is installing at least 8 different packages, and I'm not going to check each one in turn :-(
Rightio. Have been playing more. Seems just flake8 getting to a block on trying to call home.
pip install -vvv --no-binary ':all:' flake8
Seems to get stuck Cleaning up:
[cooper:~:]$ strace -p 313601
strace: Process 313601 attached
connect(3, {sa_family=AF_INET6, sin6_port=htons(443), inet_pton(AF_INET6, "2a04:4e42::223", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28^Cstrace: Process 313601
...
Successfully installed certifi-2019.3.9 chardet-3.0.4 docutils-0.14 idna-2.8 intreehooks-1.0 pytoml-0.1.20 requests-2.21.0 urllib3-1.24.3
Cleaning up...
Cleaned build tracker '/tmp/pip-req-tracker-lcudynom'
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Running command /home/cooper/virtualenvs/test_gcc_pars/bin/python3.6 /home/cooper/virtualenvs/test_gcc_pars/lib/python3.6/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp02kkwgy7
The file description seems not to be valid rst for PyPI; it will be interpreted as plain text
<string>:25: (WARNING/2) Cannot analyze code. Pygments package not found.
Seems to be entrypoints - It's using a toml + depends on flit: https://github.com/takluyver/entrypoints
flit is also all toml'd.
it seems some sdist builds won't work if they can't phone home to https://pypi.org/.
So, it seems like this is happening because those builds are reaching out to the https://pypi.org.
There's basically nothing that pip can do here -- we don't control the build process of package sdists, and the best move here is to try and identify which package is trying to reach out to PyPI (for checking the description, based on the output from the above) and requesting them to remove that bit since it's problematic to your workflow.
Closing this out, since I don't think there's anything we can do for this on pip's end basically.
Environment
Can try in Python 3.7 if required, but I'd expect that same behavior here.
Description With a pip.conf in the root of a venv to point at a PEP381 mirror it seems some sdist builds won't work if they can't phone home to https://pypi.org/. I'd like to see if this can be optional / data can be pulled from a PEP381 mirror.
Expected behavior Fetch the data from the local mirror.
How to Reproduce
pip.conf
like abovepip install --no-binary ':all:' coverage black mypy flake8 pylint
Output
Stdout:
Error:
/tmp file I see that gets created
strace + tcpdump