The building distributions docs states:

Naively, you might think that a python_distribution publishes all the code of all the python_source targets it transitively depends on

I really like how pants is smart when it builds wheels via

pants package

. However, I'm working on a plugin that requires me to build a wheel file that has all source from a set of source roots present in it. This wheel shouldn't point at any third party or first party dependencies. Is there a

Get

that I can write to convince pants to build this "uber-wheel" file for me?

If you're writing a plugin you can do whatever you want, even this abuse of the wheel format 🙂 I assume you're not planning to publish these wheels and they are purely a deployment format?

Correct on both accounts. I won't be publishing this wheel file. It's just for a one-time run. PEX almost fits my use case. However, I'll be running this artifact on a remote system that already has all of the 3rd party dependencies installed so bundling 3rd party dependencies and uploading the PEX file results in unnecessary bloat

[Shakes fist at Databricks for not supporting PEX]

A python_distribution() target will build a wheel containing all the code it depends on, transitively, that is not owned be some other python_distribution() target.

Yeah, I saw that on the "building distributions" page too and that's a really cool feature. Unfortunately, we are publishing multiple wheels. It's just that we also have a use case where it'd be great to just make an uber-wheel that holds our source files and doesn't reference any other 1st or 3rd party dependencies

Ah, so this will require a plugin, ya

Yep. So back to this question. Do you have any pointers on which internal pants things I could potentially re-use for this plugin? I have a

PythonSourceFiles

which has all of the target sources and source roots

This is all about setup.py generation, right? You could do this today if you wrote your own (simple in this case) setup.py

I'm not sure that I follow. The main goal is to get all of the sources into a single wheel. Does creating a simple setup.py by hand achieve that?

I think it would be a very simple one, yes

Hi, thanks for your input on this. We decided to just go with the simplistic "push multiple wheels" approach as that was easier than trying to configure multiple wheel distributions for each project