I would like to change how I'm telling pants how to disambiguate some dependencies. Instead of:

python_tests(
    dependencies=["st2common/tests/unit/base.py"],
)

or even a more specific version

python_tests(
    overrides={
        ("test_db_auth.py", "test_db_pack.py", "test_db_rbac.py", ...etc): {
            dependencies=["st2common/tests/unit/base.py"],
        },
    },
)

I wish I could do this instead:

python_tests(
    module_dependencies_map={
        # specify the whole import
        "tests.unit.base": "st2common/tests/unit/base.py",
        # or just the top level module:
        "tests": "st2common/tests",
    },
)

ie - tell the inference layer which file to use when it encounters a given uninferrable import (probably because it is ambiguous across the monorepo). Thoughts? Does anyone else like this UX? How feasible is something like this?

Are you sure source roots are set up correctly? Fwict, this is only adding the st2common prefix in front, right?

It is ambiguous because there is a tests module in several places in the repo.

So perhaps an option to ignore certain source roots in various places.. I wonder if the visibility feature I’m working on would work to exclude unwanted stuff in this case.. 🤔

Wow. Yeah. Visibility could probably resolve this. 🤔 I'll add a note.

@proud-dentist-22844 yes, thanks. I’ll write some tests for those see how it fits 🙏