Hi, I’m trying to setup Pants in an existing monorepo. We have a use-case which I’m not sure is handled correctly by pants: 1. We have multiple repos, one of which is a mono-repo. 2. In repo A (not not a mono-repo), we produce a package called

internal.db

(where

internal

is a namespace package). 3. In repo B (which is the mono-repo where I try to integrate Pants)

internal.db

is in use and other packages under the

internal

namespace are produced. I think there is a conflict since

internal

is partially defined inside the mono-repo and partially outside. The error I get is of the following form (I get lots of them and they come in pairs:

15:44:04.72 [WARN] The target internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources imports `internal.db`, but Pants cannot safely infer a dependency because more than one target owns this module, so it is ambiguous which to use: ['//:root#internal-db', 'internal_analytics/internal/__init__.py:../internal-analytics-src-sources', 'internal_athena/internal/__init__.py:../internal-athena-src-sources', 'internal_data_science/internal/__init__.py:../internal-data-science-src-sources', 'internal_logs/internal/__init__.py:../internal-logs-src-sources', ..., 'internal_sqs/internal/__init__.py:../internal-sqs-src-sources'].

Please explicitly include the dependency you want in the `dependencies` field of internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources, or ignore the ones you do not want by prefixing with `!` or `!!` so that one or no targets are left.

Alternatively, you can remove the ambiguity by deleting/changing some of the targets so that only 1 target owns this module. Refer to <https://www.pantsbuild.org/v2.14/docs/troubleshooting#import-errors-and-missing-dependencies>.
15:44:04.72 [WARN] Pants cannot infer owners for the following imports in the target internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources:

  * internal.db (line: 11)

I’ve tried adding the follwing to the root

BUILD

file but it didn’t fix it:

__defaults__({
  python_requirements: {
    "module_mapping": {
      "internal-db": ["internal.db"],
    }
  }
})

And

internal-db

is in Pants’ req file. I’ll try to setup a repro, but not sure when I’ll be able to…

maybe u can use

python_requirements

module_mapping

attribute to tell pants that the internal package coming from repo A, only exposes the 'internal.db` module/namespace and not the entire

internal

ns/package:

python_requirements(module_mapping={"internal": ["internal.db"]})

Thanks anyway 😛

Looks like the problem here is the opposite one - multiple packages (one published one from repo A and several local ones in repo B) provide the

internal

package, so Pants doesn’t know which one to select for dep inference.

Will give it a try now. Also, if you think it is a “good-first” PR, please LMK and I’ll try to make a repro and a fix PR in the coming days.

Thanks!

Hi, I’ve made a repository with a reproduction. Note that it is on the

namespace_collision_example

branch. The

README.md

(linked) has the details. Please LMK if you know how to fix it or if I can do anything to help fix it or to provide more details. Thanks 🙂

Yep, looking at this now. thanks for the repro!

I’ve fixed all of the other warnings, now I’ve left only with the warning of this type

@high-magician-46188 would you mind moving this convo to github discussions? I have a feeling it’s going to come up in the future, and having the conversation and fix documented would be really good. We’re running up against the limitation of Slack’s ephemerality for this sort of thing

Done: https://github.com/pantsbuild/pants/discussions/17286