Hi Team: Is it possible to disable dependency inference per build target?

Hello! Not per target, only a global option. What's the motivation?

We have code that uses dynamic loading of Python modules. I want to take advantage of dependency inference except few places in the code.

Ah I mispoke, the way you would disable dep inference is using

!

ignores. See the tooltip at https://www.pantsbuild.org/docs/targets#dependencies-and-dependency-inference

Thanks for your answer.

@fresh-architect-74417 is dep inference causing harm for those targets? Or is it just missing the dynamically loaded deps? Because you can always leave dep inference on and just manually add the deps it can't figure out from

import

statements

I still going through pants v2 for a major upgrade. This is one of the issues we have. We have a code that imports a Python module called dev_constants. That file is used in some code like this:

if env == 'dev':
    import dev_constants

We don't include it in the BUILD file so it doesn't go to our production code. We also have code that uses importlib to dynamically import some of the libraries on the fly. I want to have the ability to disable or enable imports in the build file. I will try to exclude them and see if they are going to work better.

Ah, makes sense. So you do need to exclude it explicitly.

If they all follow a consistent naming pattern, (e.g.

dev_*

) that could help too (for a generic exclude thingy…)