Which fields have people `parametrize`d on a

python_distribution

? I think it might make sense for

interpreter_constraints

, and maybe

output_path

(esp if using a parametrize group). But what about all the other fields? Is there a use case for parametrizing them? These are the

python_distribution

fields in pants core:

interpreter_constraints

,

dependencies

,

entry_points

,

provides

,

generate_setup

,

wheel

,

sdist

,

wheel_config_settings

,

sdist_config_settings

,

env_vars

,

long_description_path

,

output_path

And plugin fields on it include:

repositories

,

skip_twine

,

uses_mypyc

I thought there might be a case for

dependencies

, that it might be useful for python packages which ship compiled bins in them (like psycopg2/psycopg2-bin) or otherwise alternative deps (urllib3 vs urllib3-future). I'm not really convinced that would work well though...