I haven't seen that tutorial recently, but it should run in "check-only" mode, so it doesn't try to add/re-write any code

how do I do that

You're missing targets

So, like...

./pants --changed-since=origin/main fmt

Will run format only on changed files

Alternatively:

./pants fmt ::

will run format on all targets

Following the CI doc, you need the

changed-since

piece for your original command to work

so like this

./pants --changed-since=origin/main tailor ::  --changed-since=origin/main update-build-files  ::

i think i need to split these two commands right

You can chain commands, so following the tutorial: https://www.pantsbuild.org/docs/using-pants-in-ci#approach-1-only-run-over-changed-files

❯ ./pants \
  --changed-since=origin/main \
  tailor --check \
  update-build-files --check \
  lint

That's 1 line, multiple commands

This provides some information on running goals: https://www.pantsbuild.org/docs/goals#running-goals

so what i found out is

./pants --changed-since=origin/main tailor \ --changed-since=origin/main update-build-files

can't be run together due to this

You used `--changed-since` at the same time as using directory arguments. You can only use `--changed-since` or use normal arguments.

You only need changed-since once and it applies to both goals.

Hi! This must be something stupidly simple that I am missing, but I have some Dockerfiles in my repo that I want ignored, but I can't just edit them out of the BUILD file, because then "tailor --check" complains. Is there a solution except renaming the files to something else? (Interestingly, renaming to __Dockerfile doesn't help, only something like D__ockerfile 🙂 )

Aha, OK. I missed that while afk for a ~week. I responded on that thread and filed https://github.com/pantsbuild/pex/issues/2001

Did someone say "Faster `./pants run file.py`, please!"

I migrated some code to a Pants project, and it has some weird structure. The issue is that running lint shows some messages that don't have source references, and I don't have direct references in the code to those modules. Does anyone know? These are reported by pylint, but I suppose that somehow pylint gets to run on something that is not in the source code?

*************

<?>:16:4: W0622: Redefining built-in 'exit' (redefined-builtin)

*************

<?>:4:4: W0611: Unused import _pytest.mark (unused-import)

*************

<?>:5:4: W0611: Unused import _pytest.recwarn (unused-import)

Re: Mypy third party type stubs. How can I ensure these versions are consistent with my normal resolve versions?

I have several libraries in a monorepo. If I run "./pants package libs/lib1" it works ok, but if I run "./pants package ::" it breaks for some source file in lib1 (no python-distribution target found). Where should I look for answers to what is going on? I tried all combinations of parameters I could think of, maybe I messed the right one...

I'm so excited to generate the 4840 line pants+PEX lockfile for st2: https://github.com/StackStorm/st2/pull/5830 It really is a beautiful thing! reproducibility, here we come!

is it only here that i can’t see the tabs content at https://www.pantsbuild.org/docs/docker ? (and presumably the rest of the docs site where similar functionality is implemented) — nothing seems to happen when i click, and no errors — same seems to be true of from a phone as well — i’m fairly sure it worked as recently as yesterday

and now that i’m here — from a goal rule — is there an idiomatic way to build a request for a target that would run the equivalent of

./pants $goal $address

… i’m struggling with finding the correct way to “wrap” / hydrate my target — is there a way to achieve this without having to dig into the internals of how the run request is implemented in a certain backend?

What does an error like this mean?

stderr:
Could not find the installation RECORD for kerberos 1.3.0+krb1.16 under /d/d1/user/taymarti/.cache/pants/named_caches/pex_root/installed_wheels/c51db2b09b8517e2fdbbc7422eedacdd46162b6f2dd15ea8df4b2e99c9c9227c/kerberos-1.3.0+krb1.16-0-cp37-cp37m-manylinux2014_x86_64.whl.ad9a0577715b49b28e33fdaa8407ebcd

Is Pants doing some package metadata validation and this particular wheel doesn't ship correctly? Background: I recently found out our firm builds special wheels for the various kerberos packages (kerberos, pykerberos, gssapi, etc.) that bind specifically to

krb1.16

(so on our index, we have

kerberos==1.3.0+krb1.16

for instance). Previously we were just resolving the latest version and building the wheels locally, but that has started to have consequences as we've deployed applications to different hosts/environments, resulting in obscure errors like

ImportError: /lib64/libk5crypto.so.3 undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b

when importing

kerberos

. So we added pinned dependencies on the special wheels our firm builds. Resolve works fine, and running apps locally (without Pants) works after exporting the virtual environment. But Pants can't run/package anything depending on this, throwing the above error.

I sent a suggestion to augment the doc that would have helped me understand how

interpreter_constraints=parametrize

is related to testing multiple python versions (see my message above). I didn't know that parametrize was a targets-wide topic so I missed a key element. Hope it makes it to the official repo 🤞

https://github.com/pantsbuild/pants/discussions/17662 is starting to open Pandora's box on our plugin naming convention (specifically the path part). Have fun warming up your noodles.

I have a monorepo with several services, several libraries, many dependencies, etc and I’m having trouble trying to integrate Pants into it. I’ve simplified down to where a repo with just two folders each with a Pipfile fails to run Pants due to

ModuleNotFoundError

on any 3rd party dependencies that are shared, even if they’re the same version. How am I supposed to handle this situation?

i wanted to try out the new release

pants_version = "2.16.0.dev1"

but it does not install

BuildConfigurationError: Version mismatch: Requested version was 2.16.0.dev1, our version is 2.16.0.dev1+git57fecb6c.

Is there a straightforward way to gather information about all tests run with pants? I have about 20 individual test files that all run in parallel. Is there a way I can get a final output of all those tests that clearly mark the number of xfails, passes, skipped, etc?

If I have a PEX that supports

restartable=True

and can hot-reload, how do I do the same when running in a docker image?

PEX can ship packages and optionally can include a single console script as the entry point. Is there a way to have PEX ship multiple console scripts which can be later extracted using

PEX_TOOLS=1

? We ship a set of dependencies and sometimes they invoke commands with

subprocess

instead of a Python API. So I'm looking for an easy way to ship the console scripts for each distribution as well.