How are you running it?

If you

./pants run path/to:target_name

for a pex_binary target, it will rebuild the pex every time and run it

If you

./pants run path/to/manage.py

it will be much much faster

I assume you're using

--loop

?

Hello! I’ve been trying to play with

restartable

concept, but it seems that I misconfigure something or it’s not that powerful as I thought it is, because it restarts the app on every change in the repo not inputs only. Details in the thread 🧵.

Question about Python library packaging… I’m migrating to using pants as the build tool, how do I continue to support “extras_require”? Sounds like it might be multiple targets in some way

I just wanted to say thanks to @happy-kitchen-89482 for your explanation of monoreopos on the Real Python podcast. I've never been able to understand the allure, but with your rundown things finally "clicked" for me.

Hello, I’m running into some issues in CI which I can’t reproduce locally when running tests. Wondering if someone here knows what the cause might be. More details in the thread.

I'm working with a pre-existing pattern where python tests are in a

test

directory (I think this is pretty typical!) and there is also a utility file located in the test directory that is a dependence of the tests and not a test itself (this seems debatable as a practice, but I think should work?). I'm seeing different behavior with

sys.path

when the utility class is in a parent vs-grandparent directory of the tests.

$ tree test/
test/
├── BUILD
├── __init__.py
├── test_util.py <--- utility class, not actually a test
└── unit
    ├── BUILD
    ├── __init__.py
    ├── scripts
    │   ├── BUILD
    │   └── test_some_more_stuff.py <-- this target can *not* import test.test_util
    └── test_some_stuff.py <-- this target can import test.test_util

🧵

📣 If anyone is on the looking for conference speaking opportunities in Europe, note that Pycon Italia (Florence, Italy) and DjangoCon Europe (Edinburgh, Scotland) are scheduled to be held back-to-back. Italia's CFP is currently open, and DjangoConEu's will open soon. It's a great opportunity to propose to two excellent conferences, with the potential to have a lot of impact in a short time span. If you'd like help developing topic ideas, fleshing out a proposal, rehearsing a draft, or other assistance, feel free to ping me. I've got a lot of experience as a speaker, audience member, and program committee member; and we have others in the community who likewise do too. We want to support you. Cheers!

Do we have anyone in the community who is a wikipedia editor? I'm interested in creating a page about Pants project, but would be really grateful to have an insider's guidance on how to address the procedural hurdles.

Hi All! I'm new to pants and hoping to onboard it to my team. I'm looking to create a multi-module monorepo with Golang. I saw the docs banner saying you only support single module repos but the linked issue seems to be closed. Is multi module Golang now supported with pants? I'm sorry if I missed the answer somewhere in the docs or PR.

Hello I have a question: I ran

./pants tailor ::

in my python repo and got many BUILD files (pants v2.14), but they all contain a single line

python_sources()

with nothing else in it. I am comparing to the official python repo which has slightly more stuff in it. So is that single line all I need in almost all cases? It seems that name field has a default and if I don’t have it specified.

I have a set of code that should support python3.7 and resolver

foo

, or python3.10 and resolver

bar

. (Said resolvers already have

[python.resolves_to_interpreter_constraints]

)I then have a set of tests I want to parameterize to verify both cases actually work. In other words I want to run with (resolve=foo, interpreter_constraints=python3.7) and (resolve=bar, interpreter_constraints=python3.10) but not (foo && python3.10) or (bar && python3.7). I tired to do something like:

__defaults__(all=dict(
    resolve=parametrize("foo", "bar"),
    interpreter_constraints=parametrize(py3_7=["CPython>=3.7.1,<3.8"], py3_10=["CPython==3.10.*"])

But that generates the full matrix and pants yells with a

InvalidFieldException

about

interpreter_constraints

subsets. Is there a way to pair the parametrize or otherwise generate less than the full set of permutations? I read https://github.com/pantsbuild/pants/issues/14863 and https://pantsbuild.slack.com/archives/C046T6T9U/p1671723858955379 and I'm not sure if I should take the current state of constraints+resolves as "confusing but works" or "can't do what I want yet" (Thank you everyone for answering so many questions!)

Hi folks! Periodic reminder that we really appreciate: 1) Adding your company logo to https://www.pantsbuild.org/page/who-uses-pants (see link at the bottom) 2) Github stars at https://github.com/pantsbuild/pants These help grow the project and the community, which in turn helps us all get more features and support. Thanks!!

Hi, is there a way to get pants to output 3rd party requirements for a target in a

requirements.txt

format? It looks like

./pants dependencies

used to do this with

--type=3rdparty

(see ) but that option seems to have disappeared.

Hi, I'm not sure if I've found a bug, or I somehow misconfigure something. Subjects: Interpreter constraints. Details in 🧵.

we have a python monorepo, and each repo has a requirements.txt. We hacked together a script to combine them into a single all-requirements.txt to serve as a pseudo lockfile and use pip to install that. with potential introduction of

./pants generate-lockfile

how do we improve the workflow? Convert it to poetry? (it doesn’t seem to support monorepo) Do I still need to go through this process? it seems pants does not support a --check option currently for lockfiles so the lockfile and my requirements could go out of date.

Hey folks - I'm evaluating using

pants

for a monorepo of AWS Cloud Development Kit (CDK), an infrastructure as code tool, projects. I've got a decent prototype set up, and it looks like the

--changed-since

flag is working great. It's identifying "targets" that should be redeployed when they change. I'm struggling to figure out the best way to run a shell command on targets that have changed. For instance, this command is properly identifying code that has changed:

 ./pants --changed-since=HEAD --changed-dependees=transitive --filter-tag-regex='^cdk_app$' list
aws/projects/project_1:project_1
aws/projects/project_1/app.py
aws/projects/project_1/stack.py

Now I'd like to run a single command in

project_1

(e.g.,

cd aws/projects/project_1 && ./my-script.sh

), but I'm not sure how to best do this. In this case

my-script

would call out to the CDK binary to do the actual deployment 🧵

Hi all. I’ve got pants set up on my project, but have some questions. If I run

./pant fmt ::

multiple times in a row, it reports that changes were made each time. Why is that?

And if I run

./pants lint ::

immediately after a

./pants fmt ::

It reports that black failed, even though it succeeded immediately prior. Why does that happen?

Protobuf + Java/Scala isn't a thing right now with Pants, correct?

trying to get

./pants test <single-file>

to work: Got errors that it can’t find 3rd party libraries like sqlalchemy, google.protobuf, factory (see inside)

Hello everyone! Having some issues running the

test

goal on pants 2.14, arm64, python 3.11. Seems there is an issue building httptools wheel. Any help would be appreciated. Thanks!

Hi All -- I am struggling to get pants installed on my Mac M1 .. any ideas on how to resolve ..

[~/pants]$ /bin/bash -c "$(curl -fsSL <https://static.pantsbuild.org/setup/one_step_setup.sh>)"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1176k  100 1176k    0     0  4468k      0 --:--:-- --:--:-- --:--:-- 4632k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   162  100   162    0     0    465      0 --:--:-- --:--:-- --:--:--   465
100 19427  100 19427    0     0  46206      0 --:--:-- --:--:-- --:--:-- 46206
Bootstrapping Pants using /Users/xyz/.pyenv/shims/python3.9
Creating the virtualenv PEX.
Downloading the Pex PEX.
SHA256 fingerprint of <https://github.com/pantsbuild/pex/releases/download/v2.1.103/pex> verified.
Installing pantsbuild.pants==2.14.0 into a virtual environment at /Users/xyz/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39
Traceback (most recent call last):
  File "/Users/xyz/.cache/pants/setup/bootstrap-Darwin-arm64/pants.Spxdr9/install/bin/pip", line 5, in <module>
    from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip._internal'

Hey folks, what is your strategy (or recommend) for using

--changed-since=

in github actions when the same Test-Build workflow is triggered for both PRs and Push events?

I have a PEX question about using

--complete-platform=cp.json

with

--resolve-local-platforms

. Say I have

compatible_tags: ['a', 'b']

in my

cp.json

and I'm trying to build an sdist. Also assume my current platform can build

b

tagged wheels. I expect the build to work but it fails. Using the latest pex 2.1.119. However if I move

b

to the front of the list

compatible_tags: ['b', 'a']

, the same command works. This seems like a bug? Or am I missing something about how compatible tags are supposed to work?

Hi everyone, I'm investigating pants to see if it would work with my company's codebase as we move from a python polyrepo to a monorepo. I'm trying to build out a prototype using our code structure and running into some issues getting tests to run. I saw an issue @curved-manchester-66006 brought up yesterday and it led me here looking for any guidance.

root
├── service_1
│   ├── app_code_1/
│   │   └── module_123.py
│   ├── tests/
│   │   ├── conftest.py
│   │   └── test_app_code_1
│   │       └── test_module_123.py
│   ├── conftest.py
│   └── requirements.txt
├── service_2
│   ├── app_code_1/
│   │   └── module_123.py
│   ├── tests/
│   │   ├── conftest.py
│   │   └── test_app_code_1
│   │       └── test_module_123.py
│   ├── conftest.py
│   └── requirements.txt
└── n...

Our code is laid out in this manner (omitting the pants files) with each service in its own directory and a separate directory for tests and the application code. If I run a

./pants test ::

it successfully picks up all the tests from each service, but they all fail due to missing 3rd party imports. I ran

./pants --filter-target-type=python_requirement list ::

and it looks like it is finding all the imports from the requirements.txt

projects/service_1:reqs#pytest
projects/service_1:reqs#etc
n...

Makes me think something about how our code is organized is preventing the tests from running using the requirements file. I was also expecting that I would be able to do something like

./pants test /service_1/:

but that does not pickup the test directory contained inside the service, further making me think the organization is messing it up. Any guidance or direction would be helpful, I've been poking around the settings/configurations for about a day and haven't made any headway 🙂. Thanks for anyone's time

Is there a way I can easily run multiple `experimental_run_shell_command`s in parallel? For example, both of these

experimental_run_shell_commands

were identified as changed:

 ./pants --changed-since=HEAD --changed-dependees=transitive --filter-tag-regex='^cdk$' list
aws/projects/project_1:cdk
aws/projects/project_2:cdk

But if I try to

run

them, I get an error:

 ./pants --changed-since=HEAD --changed-dependees=transitive --filter-tag-regex='^cdk$' run
12:32:43.46 [ERROR] 1 Exception encountered:

  TooManyTargetsException: The `run` goal only works with one valid target, but was given multiple valid targets:

  * aws/projects/project_1:cdk
  * aws/projects/project_2:cdk

Please select one of these targets to run.

I can hack something with

xargs

like this:

export PANTS_CONCURRENT=True && ./pants --changed-since=HEAD --changed-dependees=transitive --filter-tag-regex='^cdk$' list | xargs -L1 -P 2 ./pants run

but I was wondering if there's a "better"/more

pants

-y way to do this?

is there a way to support wildcard when specifying files in

BUILD

and

dependencies

? I have a directory full of json, i had to specify each one using

file(name=.., source=..)

and then python tests I use all of these files, so I had a

dependencies=[…]

. tried wildcard in dependencies and got UnsupportedWildcardError