aloof-angle-91616
06/11/2020, 11:58 PMtensorflow==2.2.0
against a --find-links
repo with both tensorflow-2.2.0_....whl
as well as tensorflow-2.2.0+xxx3yyyy10zzz0_....whl
, it reliably resolves the second one with the +tag
, not the tensorflow-2.2.0
wheel, despite requesting tensorflow==2.2.0
. how is this possible?Skipping link: none of the wheel's tags match: cp36-cp36m-linux_x86_64: <https://some-url.com/python/wheels/tensorflow-2.2.0%2Btwtr2cuda10mkl0-cp36-cp36m-linux_x86_64.whl>
beautiful--platform=linux-x86_64-cp-36-m
on the pex CLI is silently ignored if the current platform is not linux and -o <file>
is not specified.
separately, is it actually correct to be resolving tensorflow==2.2.0
to tensorflow==2.2.0+asdf
? that seems like quite surprising behavior, because if anyone wants to upload a tagged +asdf
version for testing, the tensorflow==2.2.0
requirement suddenly redirects to the new tagged version. is there a workaround for this behavior so that tagged versions aren't resolved?tensorflow==2.2.0
prefers 2.2.0+asdf
over 2.2.0
enough-analyst-54434
06/15/2020, 9:20 PMaloof-angle-91616
06/15/2020, 9:20 PM+tagging
now.