I want to pytest my pants tests from vscode. is this possible to do in a good way? (I see here I can’t exactly run pants from vscode) when I saw this documentation I tried

./pants export ::

and got some interpreters for tools under

virtualenvs

as well as a

virtualenv

that comes with message

Wrote virtualenv (using Python 3.10.8) to dist/export/python/virtualenv

. the pytest env had pytest and some dependencies on my project’s sources, but it was missing numpy, which is a transitively required third party dependency. am I doing something wrong?

There's not much to go on there! I think that explains the lack of response. So, you'd want to point the IDE at your project's venv and not the tool pytest venv . By default that resolve name is `python-default`; so `./pants export --resolve=python-default`which will get you a venv for your project at `dist/export/python/virtualenvs/python-default/`to use. If that venv does not include pytest itself you'll need to add deps for it as a hack.

ok, i appreciate the help. i thought i had given enough details in my post for someone more familiar with this problem to help. what other details would you like?

Well, 1st off, reporting back if my suggestion just above worked.

export

doesn’t recognize the flag

--resolve

. the flag doesn’t seem to be documented: https://www.pantsbuild.org/docs/reference-export

Ah, sorry. I had tested in a repo I'm developing in and forgot I was on 2.15.0rc0: https://www.pantsbuild.org/v2.15/docs/reference-export#resolve

I can give it a shot

Great. Rememer,

python-default

is just the default resolve name with you enable_resolves (https://www.pantsbuild.org/docs/reference-python#enable_resolves), if you've set up a custom resolve name, use that.

we don’t have

enable_resolves

in any pants configuration

Even in 2.14.0 if you have enabled resolves, export will export venvs for all tools plus your resolve - the default

python-default

. The 2.15 improvement is to be able to export just 1 venv instead of all tools venvs + all your own.

ah, why is it not true by default then 😆 i’ll try

@glamorous-accountant-97217 it was experimental for a while then graduated. If you flip a default you break people. We don't take that lightly. There is a balance between having good defaults and breaking people / trying to correct past mistakes.

i’ve set

enable_resolves = true

,

rm -rf ~/.cache/pants ~/.pex dist .pids .pants.d

, then

./pants generate-lockfiles --resolve=pytest

and

./pants export

. The only outputs I get are my test tools in dist/export/python/virtualenvs/tools/

So, a 1 time step after enabling resolves is generating the lock file.

I was doing

./pants generate-lockfiles --lockfile=pytest

already. i need to remove the flag

So, sorry - to be clear you absolutely do not want pytest

ok i have the env, but I see it’s missing

pytest

as you said it might. isn’t that the correct behavior since my project itself shouldn’t depend on pytest?

isn’t that the correct behavior since my project itself shouldn’t depend on pytest?

Yes, it's the correct behavior. Just not useful for you. So this is where I led with "If that venv does not include pytest itself you'll need to add deps for it as a hack."

i was trying to ask whether i had the right behavior 😛 I forgot you called this a hack. i’ll try it