To clarify the role of B_dist - it's just a way of providing metadata that gets passed to

setup.py

. Depending on it doesn't do anything. If you want to depend on a published version of B then you do so like any other "3rdparty" requirement (but you have to have published it first). But I'm guessing that's not what you want? Typically since

A/tests

and

B

are in the same repo you would have

A/tests

depend on

B

as an internal dependency. That is,

A/tests

's

python_tests

should depend on B's

python_library

(not its

python_distribution

). Then the test can invoke B's code directly (rather than spawning a process to run it).