Hi, have a question on tasks. We're working on some support for publishing python targets, and running into some issues with the wiring. We have the following: `job_target`: this is conceptually similar to a

python_binary

. Thas a single 'main'

python_library

, an entrypoint, and some other params `publish_task`: this is similar to the existing publish, but uses twine. All these steps work well individually. The issue here is getting them to play nicely with each other. What I'd like to do is call our

deploy-job

goal with the

job_target

as a target. This would then in turn call our publish goal, which calls setup.py. The issue that I'm running into is that when setup.py is called, it fails with the error :

FAILURE: setup-py target(s) must provide an artifact.

I imagine this is because it is looking at the

job_target

for a provides argument, which it doesn't have. What we're looking for is to somehow specify that the

round_manager.require_data('python_dists')

line can inform setup.py libraries that this needs to be run against are the python_library deps of

job_target

I've dabbled in the python_binary code to see how this is done, but couldn't exactly grab a hold. Happy to provide more details as well