This is probably easy enough to test out, but mayb...
# generalh
high-yak-85899
04/12/2022, 5:13 PMThis is probably easy enough to test out, but maybe someone already has a quick answer. Let's say in one repo I want to make a distribution (D1) that includes modules A and B and another distribution (D2) that includes modules B and C. Now, in another repo, I want to depend on both D1 and D2. Does that cause problems given the mutual definition of B or are they isolated in some way?
✅ 1
h
hundreds-father-404
04/12/2022, 5:14 PMIf you are using pants to generate your set up files, it does some fancy logic to figure this out for you https://www.pantsbuild.org/docs/python-distributions#mapping-source-files-to-distributions
h
high-yak-85899
04/12/2022, 5:15 PMYeah, I would be. I'm more curious what happens on the repo that's using D1 and D2.
e
enough-analyst-54434
04/12/2022, 5:28 PMPants refuses to multiple package B. It will error if its amiguous whether D1 owns B or D2 owns it. If that happens, you'll pretty much be forced to define a
python_distributuon👍 1
enough-analyst-54434
04/12/2022, 5:28 PMThose docs say all that of course.
enough-analyst-54434
04/12/2022, 5:30 PMThis was a lesson learned and a hard opinion gained after dealing with the JVM jar ecosystem in the early days of Pants. In that ecosystem, re-packaging things you don't own is commonplace and leads to super-mysterious errors at runtime.
h
high-yak-85899
04/12/2022, 5:34 PMGot it. Makes a lot of sense.