Hi All, i have an issue I'm hoping you can help with. I have a test which implicitly depends on a 3rd party package (

ssh-python

which isn't inferred). I've manually added the dependency to the test, and when I run

pants dependencies --transitive <my-test.py>

i can see the package listed in the output, but when i run

pants test <my-test.py>

the test fails with a

ModuleNotFoundError: No module named 'ssh.channel'

oddly enough, if i export my pants resolve to a venv and run pytest within it, the same test succeeds. I suspect what's happening here is that another transitive dependency in my closure is exposing a

ssh

package which doesn't include a

ssh.channel

module, and during export of the venv, the correct

ssh

package including

ssh.channel

is overwriting the incorrect

ssh

package. I also suspect that the reason

ssh-python

isn't being inferred is because pants is identifying this other theoretical

ssh

-exposing package as a dependency instead of

ssh-python

My question is: how to i get pants to tell me which python import symbols map to which dependencies/targets?

Do you have a first-party package named

ssh

, or is it another inferred third-party dependency?

i don't have a first-party package named ssh. I thought it might be another 3rd-party dependency. I tried to sole the mystery by writing a new python file whose only content is

import ssh

and run

pants dependencies --transitive <my-file.py>

but this has led to an even bigger mystery: the output is blank! according to pants, this file which imports

ssh

has no dependencies!?

Do you have an example repo?

I suspect what's happening here is that another transitive dependency in my closure is exposing a

ssh

package which doesn't include a

ssh.channel

module, and during export of the venv, the correct

ssh

package including

ssh.channel

is overwriting the incorrect

ssh

package.

Why surmise? How about just https://www.pantsbuild.org/2.29/docs/using-pants/troubleshooting-common-issues#debug-tip-inspect-the-sandbox-with---keep-sandboxes and actually look in the venv and see what's in there?

Thanks @brief-scientist-13682! i forgot about that option! I've got the sandbox, but I'm not really sure what I'm looking at here... I think i've figured out where the site packages get deployed during a run, but this site-packages folder matches the exported venv. if I run the

__run.sh

script, i get the

ssh.channel

import error, but if i directly run

<sandbox dir>/.cache/pex_root/venvs/1/<hash>/<other hash>/bin/python

, I'm able to import

ssh.channel

without error...

@stale-twilight-79248 well trod ground. You don't really understand your own pytest usage fully: https://pantsbuild.slack.com/archives/C046T6T9U/p1764445356139009?thread_ts=1764196876.676159&cid=C046T6T9U

:; pants test src/uoft/core/tests/regression_tests.py
...
=========================== short test summary info ============================
FAILED src/uoft/core/tests/regression_tests.py::test_module_imports - ModuleNotFoundError: No module named 'ssh.channel'
======================== 1 failed, 2 warnings in 0.67s =========================

So, just

touch src/uoft/__init__.py

and:

:; pants test src/uoft/core/tests/regression_tests.py
...
=========================== short test summary info ============================
FAILED src/uoft/core/tests/regression_tests.py::test_module_imports - ModuleNotFoundError: No module named 'uoft.scripts.stg_ipam_dev.__main__'
========================= 1 failed, 1 warning in 0.75s =========================

And, FWICT that is a legitimate error pointing out a stale test.

oh for crying out loud! Thank you so much @brief-scientist-13682, you know, the sad part is, i should have known about this. i did attempt to arrange my monorepo as a set of pep420-namespaced packages once, years ago, and i remember now encountering this very problem and fixing it with a pytest.ini config (which is long since gone), but i had forgotten all about it