Hi. We have introduced Pants in our monorepo project recently and it works fine with python, but we also have projects written in Go. We use go 1.18 with new feature Workspaces, so part of our internal libs are resolved in

workspace.go

, but not in

go.mod

Every lib has own

go.mod

. I have found this https://github.com/pantsbuild/pants/issues/13114#issuecomment-1185321565 comment and not sure, that I’m getting the point. Right now, I cannot build/run the service, because the

lib

is not found. I have tried with

go_third_party_package(
    name="psykhe-common",
    import_path="go/lib/common",
)

but

go_third_party_package

is expected to be generated from

go.mod

file.

Note: for now, Pants only supports repositories using a single

go.mod

. Please comment on #13114 if you need support for greater than one

go.mod

so that we can prioritize adding support.

Does it mean that I cannot use pants for managing GO projects because I have more than 1

go.mod

file in the monorepo?

Correct, Pants only supports one

go_mod

target in a repository. It simplified the dependency inference feature back when bootstrapping the initial version of the backend. Easier to wait until someone actually needed the feature to then invest further work in the backend.

Yes, because we could use

replace

for internal libraries

(irony: The backend would also have to support

replace

in that case. Which I started to do a while back but would need to continue the work. https://github.com/tdyas/pants/tree/golang_handle_replace)