I can also see the use for

--(no-)tty

flag for manually setting

sys.stdout.isatty()

. Doing that would force all the "dynamic" defaults to switch at the same time. Some tools do this by using language that invokes where the command is being run, e.g.

--ci

,

--term

, etc., where each one of these represents sane defaults for a number of different configuration variables. My company actually has a number of

pants.*.ini

files where

*

is "mac", "jenkins", etc. That's how we solve the need for different configurations being run in different environments.

My company actually has a number of pants.*.ini files where * is “mac”, “jenkins”, etc.

Cool, this is an encouraged pattern.