getting the following error when trying to bootstrap the latest 2.16 dev release (dev5):

asher@ip-10-1-201-65 ~/projects/toolchain (pants2.16)$ ./pants generate-lockfiles
Bootstrapping Pants using /data/home/asher/.pyenv/versions/3.9.12/bin/python
Installing pantsbuild.pants==2.16.0.dev5 into a virtual environment at /data/home/asher/.cache/pants/setup/bootstrap-Linux-x86_64/2.16.0.dev5_py39
ERROR: Ignored the following versions that require a different python version: 2.12.0.dev2 Requires-Python ==3.7.*
ERROR: Could not find a version that satisfies the requirement pantsbuild.pants==2.16.0.dev5 (from versions: 0.0.17, 0.0.18, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33, 0.0.34, 0.0.35, 0.0.36, 0.0.37, 0.0.38, 0.0.39, 0.0.40, 0.0.41, 0.0.42, 0.0.43, 0.0.44, 0.0.45, 0.0.46, 0.0.47, 0.0.48, 0.0.49, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.62, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.0.73, 0.0.74, 0.0.75, 0.0.76, 0.0.77, 0.0.79, 0.0.80, 0.0.81, 0.0.82, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.28.0, 2.5.0, 2.5.1rc5, 2.5.1rc6, 2.5.1, 2.5.2rc0, 2.5.2rc1, 2.5.2rc2, 2.5.2rc3, 2.5.2, 2.6.0rc0, 2.6.0rc1, 2.6.0rc2, 2.6.0rc3, 2.6.0rc4, 2.6.0, 2.6.1rc0, 2.6.1rc1, 2.6.1rc2, 2.6.1rc3, 2.6.1, 2.7.0rc0, 2.7.0rc1, 2.7.0rc2, 2.7.0rc3, 2.7.0rc4, 2.7.0rc5, 2.7.0, 2.7.1rc0, 2.7.1rc1, 2.7.1, 2.7.2rc0, 2.7.2rc1, 2.7.2rc2, 2.7.2, 2.8.0.dev5, 2.8.0rc0, 2.8.0rc1, 2.8.0rc2, 2.8.0rc3, 2.8.0rc4, 2.8.0rc5, 2.8.0rc6, 2.8.0, 2.8.1rc0, 2.8.1rc1, 2.8.1rc2, 2.8.1, 2.9.0.dev0, 2.9.0.dev1, 2.9.0.dev2, 2.9.0.dev3, 2.9.0.dev4, 2.9.0rc0, 2.9.0rc1, 2.9.0rc2, 2.9.0rc3, 2.9.0rc4, 2.9.0rc5, 2.9.0rc6, 2.9.0, 2.9.1rc0, 2.9.1rc1, 2.9.1rc2, 2.9.1, 2.9.2rc0, 2.9.2, 2.10.0.dev0, 2.10.0.dev1, 2.10.0.dev2, 2.10.0.dev3, 2.10.0rc0, 2.10.0rc1, 2.10.0rc2, 2.10.0rc3, 2.10.0rc4, 2.10.0rc5, 2.10.0, 2.10.1rc0, 2.10.1rc1, 2.10.1, 2.11.0.dev0, 2.11.0.dev1, 2.11.0.dev2, 2.11.0.dev3, 2.11.0rc0, 2.11.0rc1, 2.11.0rc2, 2.11.0rc3, 2.11.0rc4, 2.11.0rc5, 2.11.0rc6, 2.11.0, 2.11.1rc0, 2.11.1rc1, 2.11.1rc2, 2.11.1rc3, 2.11.1, 2.12.0.dev0, 2.12.0.dev1, 2.12.0.dev3, 2.12.0a0, 2.12.0rc0, 2.12.0rc1, 2.12.0rc2, 2.12.0rc3, 2.12.0, 2.12.1rc0, 2.12.1rc1, 2.12.1rc2, 2.12.1rc3, 2.12.1rc4, 2.12.1, 2.13.0.dev0, 2.13.0.dev1, 2.13.0.dev2, 2.13.0.dev3, 2.13.0.dev4, 2.13.0.dev5, 2.13.0a0, 2.13.0a1, 2.13.0rc0, 2.13.0rc1, 2.13.0rc2, 2.13.0rc3, 2.13.0, 2.13.1rc0, 2.13.1rc1, 2.13.1rc2, 2.13.1, 2.14.0.dev0, 2.14.0.dev1, 2.14.0.dev2, 2.14.0.dev3, 2.14.0.dev4, 2.14.0.dev5, 2.14.0.dev6, 2.14.0a0, 2.14.0a1, 2.14.0rc0, 2.14.0rc1, 2.14.0rc2, 2.14.0rc3, 2.14.0rc4, 2.14.0rc5, 2.14.0, 2.14.1rc0, 2.14.1, 2.15.0.dev0, 2.15.0.dev1, 2.15.0.dev2, 2.15.0.dev3, 2.15.0.dev4, 2.15.0.dev5, 2.15.0a0, 2.15.0a1, 2.15.0rc0, 2.15.0rc1, 2.16.0.dev0, 2.16.0.dev1, 2.16.0.dev2, 2.16.0.dev3, 2.16.0.dev4)
ERROR: No matching distribution found for pantsbuild.pants==2.16.0.dev5
asher@ip-10-1-201-65 ~/projects/toolchain (pants2.16)$ pyenv versions
  system
  3.6.10
  3.7.10
  3.8.2
  3.8.5
  3.8.6
  3.8.9
  3.8.12
  3.9.4
* 3.9.12 (set by /data/home/asher/.pyenv/version)

This was a bug last time it came up in here. Not sure which release the fix was slated for.

never encountered that but in our (toolchain) internal repo.... but maybe I am missing something.

Oh actually it was an issue when linting test files. Running them should not need it (as you’ve said).

we use pylint and mypy both will complain if a 3rd party dep is missing. I am 99% pants will include those deps in the env it runs those tools in.

@glamorous-cpu-22971 is pytest in your requirements.txt, or however you're generating requirements?

If not, that would explain the issue

Hey @happy-kitchen-89482 - it’s not in requirements.txt (yet) although I do see it specified in the default pytest lockfile…

I hesitated to add pytest to the requirements.txt file because that list seemed to be used for application dependencies rather than test dependencies.

It looked like there was a specific version of pytest being used as the test runner, and I didn’t know if it was important that the version of pytest my test sources imported used the same version as the runner. In practice it obviously didn’t matter, but I’m trying to learn the “right” way to do things in a pants world.

When I’ve set up projects with pip I would often have two requirements files, one for the application sources (conventionally requirements.txt) and for the test sources (conventionally requirements-dev.txt)

you don't need to do that when using pants. you can have a single

requirements.txt

and when creating deploy-able targets (like wheels, pex files, etc...) pants will only include the needed deps. (because of dep inference). This is not how most stuff works in the python eco-system, since in a lot of projects you have multiple reqs files trying to manage the different things that needed to be done with each (generating docs, tests, linters, etc...) it is a PITA to manage those and Pants makes it so much easier. one reqs file for the entire repo and pants only takes the actual things that are needed from the file.

Nice! This makes total sense.

And it sounds like the path forward is clear, but just to confirm, even though

pants

2.14 does seem to bundle in

pytest

at version 7.0.1 to run the tests, it’s not possible to reference this bundled version when you’re explicitly doing

import pytest

inside your test sources (we’re doing it to import an assertion or something)

So you have to sort of “re-declare” an explicit dependency on

pytest

if you use it in your test sources.

I recently had work with this SW https://gitlab.com/BuildGrid/buildgrid and it use the multiple reqs file way/ such a PITA to manage that https://gitlab.com/BuildGrid/buildgrid/-/tree/master/requirements I got used to working with pants and forgot how painful it can be to deal with that way of ding things.

you can reference pytest... this is what

import pytest

does if you need a specific version pytest (since you need specific APIs) you may need to also specify that version under the pytest options here: https://www.pantsbuild.org/docs/reference-pytest#version

there is also https://www.pantsbuild.org/docs/reference-pytest#extra_requirements where you can specify pytest plugins.. which will be available to all tests in the repo.

I guess my question is how to do specify that in the

dependencies

field of my

python_tests

target.

(see example at thread root)

you shouldn't need to do that.

The

import

is getting resolved successfully when the tests run - my type checker is complaining, that’s the issue.

It sees an

import

statement with no corresponding dependency in the graph (or I assume that’s whats happening)

that sounds like a bug. removing that dep from the python_tests target and running

./pants dependencies

does pants see the pytest dep ?

are u using mypy ?

Yes

(and that dependency isn’t real, I just don’t know what to put there)

you can tell mypy to ignore missing imports (we do that internally, I just checked)

Screenshot 2023-01-17 at 11.47.34 AM.png,Screenshot 2023-01-17 at 11.47.43 AM.png

Yup, for sure - I guess I was wondering if there was a way to do that without silencing the warning.