This same code used to look for

pants.ini

. I think we switched away from looking for that config file since a mjor goal was to reduce the amount of config needed to get pants running, ultimately with a goal of not needing a

pants.ini

. I think we could revisit though. At some point it would be nice to have pants as a user / system binary much like heron-pants that multiple repos could share instead of installing a pants script in each repo running pants. In that world, touching pants.ini arguably seems like a low overhead repo setup step.