For the name of

python_binary

, the built pex file name is exactly the same string of name field in BUILD, so it’s possible that I got same file name

app.pex

from

./pants binary app1:app

and

./pants binary app2:app

(if I have defined both library and binary in that BUILD, I cannot use something like

./pants binary app1

), any suggestion for the best practice of the name in

python_binary

?

For Toolchain’s codebase, where we have a lot of Django, we usually use names like

users-worker

vs.

users-worker-manage

. For Pants own repository, we have lots of Python scripts like

check_headers.py

. We name the

python_binary

the exact same thing, like

check_headers

, so we get

dist/check_headers.pex