btw I might do a demo of pants for python to my team tomorrow, what's the most compelling feature that would go into such a demo? I was looking to show a dependency graph using graphviz but i dont think support for that has been added.

It depends on why you are trying to adopt pants in the first place

Yeah, also in terms of - are the people developers? Managers? Can tailor differently to each. Also, maybe draw some inspiration from here? https://www.pantsbuild.org/spotlight/testimonials

For us it was that

pants fix lint check test ::

is all you need, and

pants export --resolve python-default

will set up a dev env. We don't have to fuss about whether our version of the linter matches the one in CI or whether someone is using a polluted dev env.

@careful-address-89803 after I ran it i got

Wrote mutable virtualenv for python-default (using Python 3.10.14) to dist/export/python/virtualenvs/python-default/3.10.14

what is your dev workflow after this? so you source bin/activate? what happens if your dev dependencies changes, do you have to re-export and re-source? can it manage python version as well?

Yeah, we either source the activate script or point an IDE at the

python

binary in that folder. When we change dev dependencies we re-export. We have an "onboarding installer" that configures a whole dev environment, including the python version. But I think https://www.pantsbuild.org/2.20/reference/subsystems/pyenv-python-provider can also install python versions for your code with pyenv. I haven't used it though