-
-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pex 1.5.1 bombs at runtime with missing deps error when extras are transitively pulled in for existing packages with concrete requirement specs in the resolve scope #616
Comments
Closed
Closed
10 tasks
Noting that pip has the exact same problem. Using 19.3.1 I find:
$ diff -u orig.requirement.txt hinted.requirement.txt
--- orig.requirement.txt 2019-11-13 16:40:26.332126971 -0800
+++ hinted.requirement.txt 2019-11-13 16:41:15.057111014 -0800
@@ -1,6 +1,7 @@
absl-py==0.8.1
apache-beam==2.7.0
avro==1.9.1
+cachetools==3.1.1
certifi==2019.9.11
chardet==3.0.4
crcmod==1.7
@@ -8,18 +9,33 @@
docopt==0.6.2
enum34==1.1.6
fastavro==0.19.7
+fasteners==0.15
funcsigs==1.0.2
future==0.18.2
futures==3.3.0
+gapic-google-cloud-pubsub-v1==0.15.4
+google-apitools==0.5.20
+google-auth==1.7.1
+google-auth-httplib2==0.0.3
+google-cloud-bigquery==0.25.0
+google-cloud-core==0.25.0
+google-cloud-pubsub==0.26.0
+google-gax==0.15.16
googleapis-common-protos==1.6.0
+googledatastore==7.0.1
+grpc-google-iam-v1==0.11.4
grpcio==1.25.0
hdfs==2.5.8
httplib2==0.11.3
idna==2.8
mock==2.0.0
+monotonic==1.5
numpy==1.16.5
oauth2client==4.1.3
pbr==5.4.3
+ply==3.8
+proto-google-cloud-datastore-v1==0.90.4
+proto-google-cloud-pubsub-v1==0.15.4
protobuf==3.10.0
pyasn1==0.4.7
pyasn1-modules==0.2.7 |
The resolve takes ridiculously long, but this now works using the pip-2020-resolver. It still fails using the pip-legacy-resolver:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
repro:
the
tensorflow-transform==0.9.0
wheel appears to specify a transitive dep on:which seems to be gumming up the runtime-side resolve in pex.
this can apparently be worked around by explicitly specifying the extra in the requirement specs:
but in current pex versions is blocked by #615 for this particular case.
The text was updated successfully, but these errors were encountered: