Example: https://www.pantsbuild.org/docs/reference-black#section-export

Which also means you can just do

--no-black-export

on the CLI

Hey there, is there any update/workaround for this particular issue? https://github.com/pantsbuild/pants/issues/11386. Basically, I'm trying to include a

python_distribution

dependency to my tests but I'm encountering errors.

ProcessExecutionFailure: Process 'Building pytest_runner.pex' failed with exit code 1.
stdout:

stderr:
Traceback (most recent call last):
  File "/home/rupsi/.cache/pants/named_caches/pex_root/unzipped_pexes/43e6213d762a85cdfe3a5ba8fae598cdd810eb99/.bootstrap/pex/pex.py", line 476, in execute
    exit_value = self._wrap_coverage(self._wrap_profiling, self._execute)
  ...
    Required by:
      FingerprintedDistribution(distribution=project 2.2.12.dev0 (/home/rupsi/.cache/pants/named_caches/pex_root/installed_wheels/77e8c4120e12fb3aa103bd258ee3da4b130ac3f6/project-2.2.12.dev0-py3-none-any.whl), fingerprint='806ca55729214217ad5f390d7d0ff6733339320b')
    But this pex had no 'SQLAlchemy' distributions.
 2: alembic>=1.7.6
    Required by:
...

but checking with

./pants --tag=e2e dependencies --transitive ::

i can see that everything should be working fine

14:05:07.96 [INFO] Initialization options changed: reinitializing scheduler...
14:05:08.39 [INFO] Scheduler initialized.
//:Jinja2
//:Pillow
//:PyMuPDF
//:PyYAML
//:SQLAlchemy
//:aiofile
...

Thanks for all your help.

Great, thank you!

fyi https://github.com/pantsbuild/pants/issues/15940 tracks making this more intuitive

What is best practice for adding PyTorch to my requirements in Pants? Right now in order to get the latest CUDA build I have to include

[python-repos]
indexes.add = ["<https://download.pytorch.org/whl/cu116>"]

in my

pants.toml

file, but this makes my

generate-lockfiles

time much much longer (probably 2-3x). I can’t figure out if there’s a way to only include this repo for the single

pytorch

requirement.

pex_binary package fails. I can’t figure out how to deal with it by looking at the error log. it could be a problem with platforms=linux-x86_64-cp-38-cp38, but I verified it in a macos environment and it installed correctly. It would be very helpful to know how to respond and investigate. https://github.com/pantsbuild/pants/issues/16055

Is this even possible to have different wheels for different platforms for a given python package fetched from two different pypi server?

Important thread about when to end Python 2.7 support:

pytest question: I have a subset of

python_test

targets which I would like to run with additional pytest arguments.

python_test

target does not have any fields for pytest arguments, and I think that makes sense to me. I can add pytest arguments via cli args or pants.toml. I would like to codify the mapping between

python_test

targets and pytest arguments. I can create a

pants.jupyter_tests.toml

and override both

tag

and

pytest.args

. This works but might lead to a proliferation of

.toml

files if we have lots of different sets of tests which require specific arguments. Am I missing another better way to configure my project?

I’m not super clear on how the filesystem interacts with

pex_binary

for Python targets. When I run a

python_test

, the only files that seem to be visible in the filesystem at runtime are those that I include with

files

or similar, but I can see everything when I’m running a Python binary. Is this the expected behavior? I’m not able to get

files

or

relocate_files

to work here, are there docs about this somewhere I missed? Specific use case is pointing Flask at a template/static folder, which I’d like to have visible from the root if possible. Other workarounds appear to be passing in a source file path to the executable itself but that complicates the open source release of this code.

I'm getting a warning message containing the following:

Ignoring '[python_setup].resolve_all_constraints' option.

I understand the source of the warning, but my question is: where is the documentation about this option, or the

python_setup

set of options in general? Searching on the website turns up nothing, and I can't seem to find anything in

./pants help

either. What is this thing?

Hello there, I’m using pants with a VSCode devcontainer. Now I’m trying to access Pylint, MyPy, Black etc. from VSCode UI, so that e.g.

Python: Run Linting

from the Command Palette works, or

Format Document

when right-clicking in the workspace. I’ve kind of got this working by adding following lines into the devcontainer.json -> "settings" after exporting the virtualenv with those tools through pants export:

"python.defaultInterpreterPath": "./dist/export/python/virtualenvs/default/3.8.13/bin/python",

"python.linting.enabled": true,
"python.linting.pylintEnabled": true,
"python.linting.mypyEnabled": true,
"python.formatting.blackEnabled": true,
"python.formatting.provider": "black",
"python.linting.pylintPath": "./dist/export/python/virtualenvs/tools/pylint/bin/pylint",
"python.linting.mypyPath": "./dist/export/python/virtualenvs/tools/mypy/bin/mypy",
"python.formatting.blackPath": "./dist/export/python/virtualenvs/tools/black/bin/black",

From previous experimenting with pants I know I got this working without having to define paths for each tool. Sadly, I forgot what I did then. What do I miss? Having to manually point each tool into one path seems prone to errors when using multiple environments. I need a way that VSCode gets a path to the virtualenvs-directory etc, so that the paths are automatically identified. Thanks for your help.

--changed-since

seems to exist on

lint

and

check

goals but not

fmt

. How about adding this? Shall I open a feature request on GitHub?

Hi all, I'm testing out the java support. Our org has artifacts stored in an artifactory instance - this is currently specified in maven - https://maven.apache.org/guides/mini/guide-multiple-repositories.html I gather the way to do this in pants is to use the

url

field on the jvm_artifact. But when I set this, it doesn't seem to do have any impact. I tried it in the example-jvm repo as well. I can try to debug this further, but wanted to check I'm on the right path here - does anyone have any experience with custom repositories?

You'll want to add this configuration to pants.toml: https://www.pantsbuild.org/docs/reference-coursier#section-repos

So:

[coursier]
repos.add = ["<https://my/repo|https://my/repo>"]

Assuming you want to keep the defaults and add your artifactory to that default list of repos; otherwise drop the

.add

to fully replace the list.

Ah that sounds good, will try it out, thanks John!

Is there a way to detect if

./pants fmt

has made actual changes or not? I'd like to use it in the pre-commit hook but I don't want to blindly run

git add -u

but just abort the commit when there are changed files.

I’m having issues with a symlink when running tests. One of the tests’ dependencies contains a symlink which pants is unable to read, so whenever I run

./pants test ::

I get:

19:03:04.06 [ERROR] 1 Exception encountered:

  Exception: Failed to read link "<path/to/symlink": Absolute symlink: "path/to/destination"

I’ve made sure that the destination file is not in the .gitignore and also added an exclusion to

pants_ignore

. Is there anything that I’m overlooking?

I'm trying out Pants 2.13 and I'm seeing a disappointing performance regression in my fundamental "let's see what's changed" CI command:

./pants --changed-since=HEAD --changed-dependees=transitive list

It's gone from about 1 min to 2 min from 2.11.0 to 2.13.0a0. I can reproduce these times pretty consistently by flipping between branches with the different versions and then killing pantsd and nuking the lmdb_store and named_caches. More details in 🧵

@enough-analyst-54434 is this a legit pex command

pex3 lock export --manylinux --output lock_file.txt  pex_lockfile.json

? if so I am getting an error. What I am trying to do is to have pex generate a lock file for a linux platform, so windows only reqs won't be there.

👋 Hi everyone! Our development machines are having some issues with SSL verification of endpoints when running pants. I have passed in command line args on other tools to ignore the ssl certs (again just for a local dev sandbox). Does

pants

have an equivalent workaround? I could not find anything in the docs. (machine is a relatively new macbook pro with m1 chip)

base) ck185129@WUSCK185129-RH6 ~ % ./pants --version
Bootstrapping Pants using /Users/ck185129/miniforge3/bin/python3.9
Creating the virtualenv PEX.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))': /simple/virtualenv/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))': /simple/virtualenv/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))': /simple/virtualenv/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))': /simple/virtualenv/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))': /simple/virtualenv/

Hey folks, we're currently building some docker images with pants, using them to contain some pex binaries. Everything is working as expected, but I've run into a bit of a snag when it comes to tagging. We want to tag the images with the same version as we are using for the pex. We obtain these versions from files kept alongside the source (in a format readable by Hatch). I'd like to be able to read these version files per-target during build and use the version in there as an image tag. I saw in the documentation that anything beyond using ENV values for tagging would likely require a plugin and I've been trying to determine what sort of rule I would need to create to hook into this tagging process.

Is it expected that pants go modules support does not work with replace directivies? I have a small go tool I am trying to move into our pants-managed monorepo and when I try to run it with

./pants run

I get lots of

could not import <http://github.com/|github.com/>... (open : no such file or directory)

. While

go run .

on the same code works fine.

👋 for shell scripts in the context of reusing build tooling, does pants offer anything out of the box for shell/coreutils isolation? so that shell scripts gets executed with gnu equivalents on both mac os and linux for instance?

Seems like it? https://github.com/pantsbuild/pants/issues/14996

ah thanks. I did a quick search and missed that one.

Hi folks! This is your periodic reminder that two easy things you can do to help the Pants community grow are: A) Star the project on GitHub and B) add your company to the Who uses Pants page (see link at the bottom)