I'm importing pytest in

conftest.py

, and I get a warning that pants cannot infer owners for pytest fixtures (tried

from pytest import fixture

as well as

import pytest

) shouldn't that be built-in?

Do you have a `python_test_utils` target in the

BUILD

file in that directory?

I do, looks like this:

__defaults__(all=dict(skip_mypy=True))

python_tests()

python_test_utils(name="test_utils", dependencies=[":fixtures"])

files(name="fixtures", sources=["fixtures/**/*"])

You may need to use

resources

instead of

files

.

If it helps, the warning shows up when I try to see dependencies of one of the test files in the same directory

reading these docs, it seems that files is the way to go for fixtures. Tried resources nevertheless, still getting the warning

could you share the full error message?

If you're asking for the full stdout I'd need to anonymize it first. But here's the relevant bit at the very beginning:

$ pants test python/cli/tests:
23:22:29.88 [WARN] Pants cannot infer owners for the following imports in the target python/cli/tests/conftest.py:test_utils:

  * pytest.fixture (line: 6)

If you do not expect an import to be inferrable, add # pants: no-infer-dep to the import line. Otherwise, see <https://www.pantsbuild.org/v2.16/docs/troubleshooting#import-errors-and-missing-dependencies> for common problems.

Are you using a resolve? And does the resolve have

pytest

in it?

for test, I'm just specifying a lockfile. Guess I'm using the default then?

And how is the lockfile generated?

[GLOBAL]
pants_version = "2.16.0"

backend_packages = [
 "pants.backend.build_files.fmt.black",
 "pants.backend.python",
 "pants.backend.python.lint.black",
 "pants.backend.python.lint.isort",
 "pants.backend.python.lint.bandit",
 "pants.backend.python.typecheck.mypy",
]

[anonymous-telemetry]
enabled = false

[python]
interpreter_constraints = ["==3.9.*"]
enable_resolves = true

[python-bootstrap]
search_path = ["<PYENV>"]

[pytest]
version = "pytest~=7.3.1"
extra_requirements = ["pytest-mock~=3.10.0", "pytest-cov~=4.1.0"]
lockfile = "build_support/pytest.lock"

[black]
version = "black[jupyter]~=22.12.0"
lockfile = "build_support/black.lock"

[bandit]
config = "pyproject.toml"
version = "bandit[toml]~=1.7.5"
lockfile = "build_support/bandit.lock"

this is my pants.toml file, I'm then generating lockfiles with

pants generate-lockfiles

that would be the issue then

ok, I'm getting there 😅

To be fair, this is a somewhat unnecessary and confusing distinction. Which is why 2.17 will allow Pants to use the version of pytest from your user lockfile for the tool invocation.

fair enough. Actually pytest is only used in tests, it should be a dev dependency IMHO

So when Pants build a binary it only uses the applicable subset of the resolve.

tried it, seems to work (weird or not :D). Many thanks for the help and explanations 🙇

right, I saw this earlier but clearly it didn't land 😄

well it only discusses merging tool/user lockfiles, it doesn't call out that any imports must be in the user lockfile.

that warning led to failed tests and misleading error messages down the line, it deserves to be an error if you ask me