This is an interesting one

our source tree looks like:

src
|__ library
|__ library2
build-support
|__ BUILD
|__ plugins
|_____ custom_target
|_____ docker

the contents of

build-support/BUILD

The contents of

src/library/BUILD

When we moved the

python_library

target in

build-support/BUILD

to

build-support/plugins/BUILD

The tests for

src/library:tests

started failing with

ModuleNotFoundError: No module named 'docker.errors'

Only if

build-support/plugins:

and

src/library:

are run together in a

./pants test

command

i suspect this is because the

docker

targeet is being used instead of the dependecies internals

Fill stack trace here

oh boy just realized i have thewrong thread title, and probably channel