So we're using python-grpc (pants supports ootb 👍 ) We're using

pytest-grpc

which we've added to our

[pytest].extra_requirements

in pants.toml... This then means any tests that don't have a transitive dependency on grpc fails. So we've added

grpcio

to our extra_requirements too... This then lead to the two versions of grpcio for the two lockfiles diverging resulting in 'fucky' behaviour in our CICD platform when the old version no longer had a precompiled binary (or our CICD platform changed their environment and was no longer able to compile it) Is there a way to avoid this?

Why do the versions diverge? Can you not pin them both to the same value?

This issue would fix your problems https://github.com/pantsbuild/pants/issues/12449 Benjys suggestion about pinning then to the same version is wise though

+1 josh

yeah, both those tickets are pretty much talking about the same problem.

Why do the versions diverge? Can you not pin them both to the same value?

We can yeah, but it's then a whole 'thing'. I think we'll just deal with it, sounds like a solution is on the way at some point.

Yeah, it’s not ideal, but is at least a workaround?

yeah