Judging by the docs and FAQ, I think this is a fairly common problem due my naive setup -- pants seems to be missing 3rd party python dependencies (requests, pandas, etc.) when testing. for example, a very rough sample of the structure, using two packages

pkg1
|_BUILD <contains poetry_requirements>
|_pyproject.toml <specifies dependency on requests>
|_pgk1
  |_BUILD <contains empty python requirements>
  |_source.py <import requests>
pkg2
|_BUILD <contains poetry_requirements>
|_pyproject.toml <specifies dependency on pkg1>
|_pgk2
  |_BUILD <contains empty python requirements>
  |_source.py <uses pkg1.source>

Here, running tests for pkg2 fails because

requests

is missing. From the docs, the solution seems to be to add these dependencies to

BUILD

files rather than relying purely on

tailor

. The only snag is I have way too many

BUILD

files to do this manually? Am I missing an easy solution?

pants should be inferring that dependencies are required from statements in the code like

import requests

, so it sounds like that's not working as expected. Some questions: • Can you share your

pants.toml

configuration? • Are there any warnings from pants when you run things? • What does

pants dependencies --transitive

show for the various files?

there are many warnings 😅

[WARN] Pants cannot infer owners for the following imports in the target llama-index-core/llama_index/core/download/dataset.py:

  * requests (line: 8)
  * tqdm (line: 9)

[WARN] Pants cannot infer owners for the following imports in the target llama-index-core/llama_index/core/llama_dataset/base.py:

  * openai.RateLimitError (line: 9)
  * pandas.DataFrame (line: 10)
  * tqdm (line: 8)

My pants.toml is

[GLOBAL]
pants_version = "2.19.0"

backend_packages = [
  "pants.backend.python",
  "pants.backend.experimental.python.lint.ruff",
  "pants.backend.python.typecheck.mypy",
  "pants.backend.python.lint.black",
]

[python]
interpreter_constraints = ['>=3.8.1']

[source]
marker_filenames = ["pyproject.toml"]

yes, resolve the warnings should fix this. The focus to resolve them should be on how the external dependencies are loaded, i.e. just the

python_requirement

,

python_requirements

or

poetry_requirements

targets. I'm not in a position to help in detail, but often having duplicate dependencies within a single "resolve" is the problem

hmm alright 🤔 thanks!

Ah, maybe https://www.pantsbuild.org/2.18/reference/subsystems/python-infer#ambiguity_resolution is relevant