howdy! i have a pip command generated by pex that ...
# pex
w
howdy! i have a pip command generated by pex that looks like:
Copy code
pip \
  --disable-pip-version-check \
  -vvvvv \
  --isolated \
  download \
  --dest \
  blah \
  --no-index \
  --find-links \
  <https://example.com/home/third_party/source/python/bootstrap/> \
  --find-links \
  <https://example.com/home/third_party/source/python/wheels/> \
  --find-links \
  <https://example.com/home/third_party/source/python/deprecated/> \
  --platform \
  manylinux2014_x86_64 \
  --platform \
  linux_x86_64 \
  --implementation \
  cp \
  --python-version \
  27 \
  --abi \
  cp27m \
  --only-binary :all: \
  --pre \
  'pytest-cov<3,>=2.8.1' \
  'pytest<3.7,>=3.0.7' \
  'zipp==1.1.0'
which fails to find
coverage>=4.4
i added the
-vvvvv
, and the relevant section appears to be
Copy code
Collecting coverage>=4.4 (from pytest-cov<3,>=2.8.1)
  3 location(s) to search for versions of coverage:
  * <https://example.com/home/third_party/source/python/bootstrap/>
  * <https://example.com/home/third_party/source/python/wheels/>
  * <https://example.com/home/third_party/source/python/deprecated/>
  Getting page <https://example.com/home/third_party/source/python/bootstrap/>
  Looking up "<https://example.com/home/third_party/source/python/bootstrap/>" in the cache
  No cache entry available
  Resetting dropped connection: <http://example.com|example.com>
  <https://example.com:443> "GET /home/third_party/source/python/bootstrap/ HTTP/1.1" 200 563
  Updating cache with response from "<https://example.com/home/third_party/source/python/bootstrap/>"
  Analyzing links from page <https://example.com/home/third_party/source/python/bootstrap/>
  Getting page <https://example.com/home/third_party/source/python/wheels/>
  Looking up "<https://example.com/home/third_party/source/python/wheels/>" in the cache
  No cache entry available
  Resetting dropped connection: <http://example.com|example.com>
  <https://example.com:443> "GET /home/third_party/source/python/wheels/ HTTP/1.1" 200 None
  Updating cache with response from "<https://example.com/home/third_party/source/python/wheels/>"
  Analyzing links from page <https://example.com/home/third_party/source/python/wheels/>
  Getting page <https://example.com/home/third_party/source/python/deprecated/>
  Looking up "<https://example.com/home/third_party/source/python/deprecated/>" in the cache
  No cache entry available
  Resetting dropped connection: <http://example.com|example.com>
  <https://example.com:443> "GET /home/third_party/source/python/deprecated/ HTTP/1.1" 200 858
  Updating cache with response from "<https://example.com/home/third_party/source/python/deprecated/>"
  Analyzing links from page <https://example.com/home/third_party/source/python/deprecated/>
  Could not find a version that satisfies the requirement coverage>=4.4 (from pytest-cov<3,>=2.8.1) (from versions: )
Removed build tracker '/private/var/folders/91/bym4mtpx1p503xmvpp8fbdl40000gp/T/pip-req-tracker-ilzUpY'
No matching distribution found for coverage>=4.4 (from pytest-cov<3,>=2.8.1)
but: we have a lot of versions available at those urls that match these requirements (afaict)... so it feels like the next thing to inspect is the tags that are involved
i have to run to something for an hour, but if anyone knows how to get pip to give me more information about why it isn't matching, that would be helpful. thanks!
(and this worked pre
pex 2.0
so it feels likely that this is a 1.6/2.0 difference)
e
You have a pre-built py27 coverage wheel?
w
Copy code
coverage-4.5-cp27-cp27m-macosx_10_12_x86_64.whl
coverage-4.5-cp27-cp27mu-linux_x86_64.whl
coverage-4.5-cp36-cp36m-linux_x86_64.whl
coverage-4.5-cp36-cp36m-macosx_10_12_x86_64.whl
coverage-4.5.1-cp27-cp27m-macosx_10_12_x86_64.whl
coverage-4.5.1-cp27-cp27mu-linux_x86_64.whl
coverage-4.5.1-cp27-cp27mu-manylinux1_x86_64.whl
coverage-4.5.1-cp36-cp36m-linux_x86_64.whl
coverage-4.5.1-cp36-cp36m-macosx_10_12_x86_64.whl
coverage-4.5.1-cp36-cp36m-manylinux1_x86_64.whl
coverage-4.5.2-cp27-cp27mu-manylinux1_x86_64.whl
coverage-4.5.2-cp36-cp36m-macosx_10_13_x86_64.whl
coverage-4.5.2-cp36-cp36m-manylinux1_x86_64.whl
coverage-4.5.3-cp27-cp27m-macosx_10_13_intel.whl
coverage-4.5.3-cp27-cp27mu-manylinux1_x86_64.whl
coverage-4.5.3-cp36-cp36m-macosx_10_13_x86_64.whl
coverage-4.5.3-cp36-cp36m-manylinux1_x86_64.whl
coverage-4.5.4-cp27-cp27m-macosx_10_13_intel.whl
coverage-4.5.4-cp27-cp27mu-manylinux1_x86_64.whl
coverage-4.5.4-cp36-cp36m-macosx_10_13_x86_64.whl
coverage-4.5.4-cp36-cp36m-manylinux1_x86_64.whl
coverage-4.5.4-cp37-cp37m-macosx_10_13_x86_64.whl
coverage-4.5.4-cp37-cp37m-manylinux1_x86_64.whl
...maybe
m
vs
mu
...?
e
Yes
Tags are exact things.
Aka, PEX 1.6 was buggy here
w
oook!
thank you sir.
sidenote: the debuggability of dumping the entire pip command is very awesome. thank you.
❤️ 1
e
You're welcome.