Really the

--sources-directory

was just added for Pants and it was probably a mistake. Any non-Pants usage will probably always want to use

setup.py

or `pyproject.toml`; ie the requirement of

.

(i.e.: the path of the directory containing

setup.py

or `pyproject.toml`for the local project).

Hi! I finished rewriting our docs for Targets to get more to the point. And to also talk about "target generation", which we were always doing since Pants 2.0 but was not explicitly modeled until Pants 2.8 (e.g.

python_tests

generating

python_test

targets) Any feedback would be welcomed! https://www.pantsbuild.org/v2.8/docs/targets

https://www.pantsbuild.org/docs/targets for the original Feel free to comment here or "suggest edits" in the top right corner 🙂

looks great: thanks.

given that the Target generators section says that we recommend using them over per-file targets, it’s odd that they are below single-file targets on the page

folks should only very rarely need to create single file targets, right?

which also means that they will overwhelmingly interact with the

sources

argument rather than the

source

argument

My thinking was: start with the simplest thing possible, the atom targets. They are the core building blocks. Also the docs are pretty simple on those. So get through those quickly Then, get into the really important parts with target generation, which end up talking up half the page

Would it help if I change the first few sections to focus more on file-less targets like

pex_binary

rather than

python_test

? The reason I didn't do that is it is more abstract

while i agree that the atoms are the most important… i think that the atom is the file, rather than necessarily the file target

and discussing how the per-file targets are implemented first, rather than what you do to create them is a bit too detailed. it’s more architecturey than “what do i put in my BUILD file”

Okay I think I can rewrite the examples to talk about target generators sooner while still saving the nitty gritty details until the end. Will fork the page. Thanks for the feedback! (Altho probably after finishing other docs changes and the blog, those seem even higher priority)

sounds good… thanks!

fwiw, i’ve a bit more experience using pants in a from-scratch `tailor`’d repo recently, and the effect of

tailor

is that ~everything renders as a file address, except tests… so particularly for new folks, i expect that they’ll think that “target” means “a file, most of the time”

I don't think this is the time and place to have this discussion, but: ack. And I've been wondering how desirable that is, whether it suggests a false friend when it's not really a file (but also mostly is) Lots to discuss/figure out in the near future!

PSA: it's now feasible to incrementally port your tests to Pants! You can combine the

skip_tests

field with this nifty query, then pipe the output into your original test runner:

./pants filter --target-type=python_test :: | \
  xargs ./pants peek | \
  jq -r '.[] | select(.skip_tests== true) | .["sources"][]'

Now documented at https://www.pantsbuild.org/v2.8/docs/existing-repositories#3-set-up-tests

Any sharp edges to watch out for when upgrading from 2.6 -> 2.8rc5? We want to test out the experimental bash target and golang support.

./pants --loop test check fmt lint

is amazing. thank you.

How can I include a multiline string in

extra_env_vars

in

pants.toml

that includes

==

(e.g public and private keys) I can add multiline values with

'''

or

"""

but if I add one that contains (or maybe just ends) in

==

then I get the following errors (see thread)

saw a weird issues with 2.8rc5 and lockfiles yesterday. Pants resolves pandas to require

python>3.7, python<=3.7.1

(I'm on a different brach right now; I'll post repro and full error message later)

hi - im running some tests with a

python_tests

target. I would like to add some regression tests that make use of data files (eg json) is there a way to have these included in the test run ? I tried adding `files`/`resources` but

python_tests

doesnt have these params, and if i try to add a non-py file to

sources

that also fails

Hello again, I'm trying to understand an issue I encountered today in pushing a docker image on Jenkins Pipeline, where

pants publish

returned an error "_denied: requested access to the resource is denied_" from docker-cli. Meanwhile a plain

docker push

worked just fine. My Jenkinsfile wraps the

pants publish

step inside withDockerRegistry. The urls specified in withDockerRegistry and in

[docker.registry.private_name].address

are identical (though Pipeline plugin requires a protocol prefix whereas pants doesn't). In our Pipeline, we use a separate credentials to login and push the image and that account is different from the pipeline runner, i.e.

$USER

. The last thing worth mentioning is that the docker images were built prior to entering withDockerRegistry, meaning that they were built under the name of

$USER

. Am I doing something wrong perhaps?

Whats the correct way to get Pants to detect changes in the

requirements.txt

the

python_requirements()

uses? Here's how my requirements are set up (see image) It looks like there was an issue around this but it looks like it's been merged (https://github.com/pantsbuild/pants/pull/9946)

Issue with example python repo on Ubuntu..

Hi folks, I'm @ about to publish a blog post outlining some of Pants's advantages over Bazel. Before I do, I'd love to get some feedback from y'all: https://docs.google.com/document/d/1y4jS4x-3YoP2x3vbPQF_O_8FoNFBR_Gu/edit?usp=sharing&ouid=116918981665275438468&rtpof=true&sd=true

Is there a good reason to cache a result when we get a

PermissionDenied

error?

Another question regarding interpreter constraints (hazy area for me..)

Is there a way to suppress warnings for a specific glob being empty? I have a files target which is globbing some files that may not exist (another repository that our makefile checks out before building that target). It would be nice to not get a warning when building without those files present (which is most of the time)

so.. weird one.. added mypy one mergerequest ago. used a lockfile, added some .pyi stubs for a library, all working. CI built and deployed. 👍 great Today, adding isort. same deal, everything (test, check, lint) working locally. But now mypy when running in CI is complaining about no stubs. looks like mypy fails when i'm using

--changed-since

╭─xlevus@xd1 ~/Projects/_mono  ‹feat/isort› 
╰─➤  ./pants check --changed-since=origin/master                                                                                                         1 ↵
11:15:00.85 [INFO] Completed: Extracting 3 requirements to build requirements.pex from repository.pex: docker, requests, six
11:15:02.36 [INFO] Completed: Building requirements_venv.pex
11:15:04.27 [ERROR] Completed: Typecheck using MyPy - MyPy failed (exit code 1).
build-support/deploy/docker_.py:3: error: Skipping analyzing "docker": found module but no type hints or library stubs
build-support/deploy/docker_.py:3: note: See <https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports>
build-support/deploy/docker_.py:4: error: Skipping analyzing "docker.errors": found module but no type hints or library stubs
build-support/deploy/docker_.py:5: error: Skipping analyzing "docker.models.images": found module but no type hints or library stubs
Found 3 errors in 1 file (checked 6 source files)



𐄂 MyPy failed.
╭─xlevus@xd1 ~/Projects/_mono  ‹feat/isort› 
╰─➤  ./pants check ::                                                                                                                                    1 ↵
11:15:13.10 [INFO] Completed: Typecheck using MyPy - MyPy succeeded.
Success: no issues found in 18 source files



✓ MyPy succeeded.
╭─xlevus@xd1 ~/Projects/_mono  ‹feat/isort› 
╰─➤  ./pants --version
2.8.0rc6

Hey trying to upgrade to pants

2.8.0

excited to use the new features. Running into this issue when building any python target that depends on proto.

Exception: Client error (404) downloading file grpc_python_plugin from <https://binaries.pantsbuild.org/bin/grpc_python_plugin/1.32.0/macos/grpc_python_plugin>