Hey pants pros, I'm forwarding <this discussion> o...
# general
s
Hey pants pros, I'm forwarding this discussion over here for visibility. TLDR: I want to use a python_distribution from one resolve in another project under a different resolve.
We're currently uploading the wheel to our internal registry, then pulling it back down from the cloud in the other project.
Other option is to parameterize the library, but that isn't great either since we don't want the lib to concern itself with any of the consumers.
Happy to discuss more in here if that's easier.
w
TLDR I believe (unless someone corrects me), this workflow still kinda sucks. I ran into this recently, and either doing what you’re currently doing, or using parametrization were the two options. However, the “correct” option is in a few GH issues or discussions that I need to dig through - where the parameterization is kinda “stopped” once a package is created. This feature was applied to some packageable goals, but I think it didn’t make it to python_distribution, as there were some quirks
I'd need to find the links themselves, as there are several related issues - but yeah, in short, what you’re doing SHOULD work without the internal registry, but it was a technical challenge
👍 1
https://github.com/pantsbuild/pants/pull/19155 I think this was one of the leafs/roots that led me down a traversal path of issues