Hello everyone, I have a question about

python_distribution

. In my monorepo, I have a package A that depends on package B (both owned by me). When I build package A, I want to build

A.whl

such that it includes

B.whl

and/or knows where to pick it up without relying on PyPI. Similar to how pip operates when we do not use the

--no-deps

option. But I noticed that the generated

A.whl

does not contain any reference to B apart from in the metadata. Does anyone know how to achieve what I want?

So you want A.whl to include the code that is also in B.whl?

Yes, I do see B in the

Requires-Dist

metadata and pip does try to install B from PyPI when I install

A.whl

. However, some of our downstream users do not have access to the internet and until we get them to use pexes, they use whls. When I use pip to generate the whls, I can leave out the

--no-deps

and the generated

A.whl

contains all the dependency whls too. We could ship individual whls to them, but is there any way to tell pants that the whls should be all-encompassing?

If you manually write the setup.py then yes

Got it, thanks! I was going to give the setuptools args in here a shot. Is that not worthwhile?

I think you will run afoul of “However, you cannot use data_files, install_requires, namespace_packages, package_dir, package_data, or packages because Pants will generate these for you, based on the data derived from your code and dependencies.”

Ahh, ok. Thank you. For packages that require an end-to-end whl, I suppose having my own setup.py is preferred.

Yeah, that’s really what Pex is for