short of disabling inference alltogether, is there a way to partition off portions of code? Through whatever process, I've noticed that things like test util code and the likes are leaking into 'production' builds. I also spent a good 30minutes trying to work out why something wasn't working, and it was because my IDEs auto-import picked the wrong class to auto-import and pants just rolled with it.

Sounds like what you want is a way to enforce dependency rules? E.g., saying "this thing may not depend on this thing"?

yeah. but probably more generically. "Things in //x/y/z can only be accessible by things in //x/y/z" or "`python_test_utils` are cannot be included in

package

targets" or something.

Sounds like https://github.com/pantsbuild/pants/issues/13393 ;)

yeah.

Yeah, the main reason we haven't done this yet is that everyone has a different idea of how to express these rules. I don't want to get into creating DSLs for this. So I'm thinking something like a custom callback.

ah yes can do

That just came up in a discussion about repo organization for me yesturday. I was planning on building some custom CI checks that look at pants dependencies output for allowed or disallowed items. But some kind of build in support in pants would be better