https://pantsbuild.org/ logo
Join Slack
Powered by
Is there any way to patch a 3rdparty dependency fi...
# general
c
Is there any way to patch a 3rdparty dependency file? currently stuck on an old version of tensorflow which pins to an old version of grpcio so currently stuck with that version when using a lock file. Would be nice to be able to change while resolving to require something else since it will work with the never version. Have thought about generating the wheels but they are big to ship around.
h
I think @hundreds-father-404’s new lockfile work will support this, as you can manually edit the lockfile to select the version you want.
New lockfiles will be actual lockfiles, as opposed to today's, which are just pip constraints files...
h
I think you should still be able to change the pinned version of grpcio in constraints.txt tho. Is that not working?
c
It's getting mad that the version doesn't aline with what tensor-flows constraint are asking for.
I can change the 
grpcio
version the resolver job will fail since it's doing 
pip -r lock.txt
under the hood and won't allow a mismatch.
Possible Erics changes will fix this if we can overwrite what the underlying package manager is doing
Error is
Copy code
The conflict is caused by:
     The user requested grpcio==1.39.0
     grpc-interceptor 0.13.0 depends on grpcio<2.0.0 and >=1.8.0
     opentelemetry-exporter-jaeger-proto-grpc 1.3.0 depends on grpcio<2.0.0 and >=1.0.0
     tensorboard 2.5.0 depends on grpcio>=1.24.3
     tensorflow 2.4.1 depends on grpcio~=1.32.0
 
 To fix this you could try to:
 1. loosen the range of package versions you've specified
 2. remove package versions to allow pip attempt to solve the dependency conflict
h
I don't think my change is relevant to this. Still will be using pip to install 
grpcio==1.39.0
and 
tensorflow==2.4.1
(what you have pinned), which will fail
c
Darn. Was hoping to not have to create new wheels
4 Views
Open in Slack
PreviousNext
Powered by