Hi I have been trying to build a package which has dependenc

Question

Hi I have been trying to build a package which has dependency on another package Although I don t see any files from the dependency I have this toy repo where I am playing around with it There are two packages `package a` and `package b` `package a` has dependency on `package b` I do see the `package b` as dependency in generated `setup py` Is this how it s supposed to work The python distribution for `package a` is defined and the

refined-addition-53644 · Answer

This is what I see locally when I unzip the generated dist ``` tar xvf dist package a 0 1 0 tar gz C unzip dist x package a 0 1 0 x package a 0 1 0 MANIFEST in x package a 0 1 0 PKG INFO x package a 0 1 0 backend shim py x package a 0 1 0 package a x package a 0 1 0 package a init py x package a 0 1 0 package a main py x package a 0 1 0 package a package a py x package a 0 1 0 package a egg info x package a 0 1 0 package a egg info PKG INFO x package a 0 1 0 package a egg info SOURCES txt x package a 0 1 0 package a egg info dependency links txt x package a 0 1 0 package a egg info namespace packages txt x package a 0 1 0 package a egg info requires txt x package a 0 1 0 package a egg info top level txt x package a 0 1 0 setup cfg x package a 0 1 0 setup py ```

happy-kitchen-89482 · Answer

Yeah I think this is working as intended How Pants decides which code goes in which distribution is explained here <https www pantsbuild org docs python distributions mapping source files to distributions>

happy-kitchen-89482 · Answer

But Pants goes to great lengths to not embed the same code in multiple distributions

happy-kitchen-89482 · Answer

so if package a has a dist and package b has a dist then pants will do the right thing by default and build a package a dist with a requirement on package b s dist

refined-addition-53644 · Answer

So in this case it means I need to make sure pants can access the `package b` as 3rd party dependency when installing `package a` right

happy-kitchen-89482 · Answer

Not sure what you mean exactly Pants should be able to build a distribution from `package b` I assume it has a `python distribution` target

happy-kitchen-89482 · Answer

So the thing is that you have to publish `package b` so that `package a` can consume it

happy-kitchen-89482 · Answer

This is the downside of using publishing as your dependency mechanism The alternative is PEX files where package a and all its deps including package b get bundled into a single file

refined-addition-53644 · Answer

yeah I meant the publishing aspect So that clears it Yeah I do think PEX is the way to go

happy-kitchen-89482 · Answer

Since pexes aren t consumed by other code it is safe for them to bundle all the deps even if multiple pexes have overlapping code as there will not be ambiguity about where a symbol should come from it comes from inside the pex

happy-kitchen-89482 · Answer

So they really are a great way to package and deploy code that isn t intended to be published and then consumed by others