So I’ve been looking into why I cannot install a particular pylint version… I’m trying to use

2.4.15

, which needs python 3.7 (which is what our repo is supposed to use). When I try to generate a lockfile it says:

ERROR: Could not find a version that satisfies the requirement pylint>=2.14.5
ERROR: No matching distribution found for pylint>=2.14.5

If I look in the logs, it says it’s using 3.7.4 to bootstrap the env, and if I check in the sandbox, the pex file is python 3.7.4. But if I run

__run.sh

, it gets changed to 3.6.8 (this was a pyenv artifact). If I use the pex from the sandbox folder to get pylint, it works. If I run

__run.sh

, it obviously stops working. There’s also nothing in the log file mentioned in the command line printed. How can I debug/fix this, except by uninstalling any

<3.6

I have?

Looking for feedback: is it wise to try to require that all files under a directory be added to some target? I know

./pants tailor

will take care of things for which the backends are installed, but I'm thinking of also requiring that even text files or json files or whatever be at least lumped into

files()

targets so that nothing is really unknown to Pants. Could this backfire?

Hi, I got this message for some tests

[WARN] Failed to generate JUnit XML data for test/python/...tests.

Do you know how I can troubleshoot this problem in Pants? I tried to find some logs and use the flag

--keep-sandboxes=always

, but without success... Note that the tests are successful. Thank you.

Hi guys, I have a question around building a Docker image from a python source. So far I have understood that if I want to publish a python library from a python source, I should be using

python_distribution()

target and for a Docker image it should be

docker_image()

target. Throwing in gRPC and Protobufs in the mixture and there I know that

python_distribution()

target type will resolve the proto dependency at the time of executing

package

goal. Would the target type

docker_image()

do the same? Is

package

the right goal for my use case here as in to build a Docker image?

🎉 https://github.com/pantsbuild/pants/pull/16560 and https://github.com/pantsbuild/pants/pull/16573 Have us supporting

BUILD

file formatters in

fmt

, instead of having to invoke

update-build-files

. They are supported by opt-in backends, and pluggable! Hopefully, 2.14 will see us moving the fixing to a new

fix

goal as well! (Also, this adds

buildifier

formatting, which is sort-of like

black

but also does keyword arg sorting. Thanks Bazel 😛)

📛 A previous lengthy 🚲 🏚️ bikeshed thread concluded that we should change the naming of "experimental" (unstable) features to something that avoids sending a message that Pants is not production-ready. Instead of calling things "experimental", we would use some other (probably novel name), and each item with this feature would have a tracking issue in GH that would explain the exact nature of the stability and release-readiness of the item at that point in time. So now we need to decide on a name. Items raised in the linked thread include the following: • `muslin`: sewing metaphor: test garment that you're making out of cheap fabric to test the fit • `basting`: another sewing metaphor: temporary stitches to hold things together until you've put in the final ones • `tacks`: another sewing metaphor: loose stitches to transfer pattern markings into fabric prior to sewing • `next`: Just a word to mean "coming soon" or something like that • `future`: Closer to what Python uses • `labs`: how startups brand themselves to present themselves as forward-thinking The chosen name would show up as something like

pants.backend.$newname.$feature

in the switches to enable the backend. Using them as a prefix in goals/targets/options would be avoided as much as possible (although we may need to discuss the finer details of this in another thread). Pants community, what's your opinion on a good name here? We can discuss here, narrow these down, and the we'll put it to a vote

Curious about some repo management philosophy: Has anyone developed or come across best practices for monorepo management as it relates to the dependency graphs? I can think of two extremes (to simplify, let's just talk about functions): 1. A module contains a huge number of functions 2. Functions are 1:1 with modules 1 is mostly a benefit for the developer. It's easy to remember where to import what they need and use new features as they become available. 2 is beneficial for build systems since you'd guarantee that you're only dependent on the functions you're using. You'd see the benefits of test caching, packaging sizing, etc. This will be very subjective, but where should the line be drawn between one and two? Separately, is their tooling that can give a sense of the ratio of things included vs. things used. I think this would be a mix of static analysis and build tooling working together. It's just a different flavor of code coverage analysis I think.

Hi guys. We are currently evaluating Pants. We are having issues adding a .whl dependency that is a simple url to an s3 bucket. The url is listed in the requirements.txt, but pants throws an error saying it can't find the file location when trying to build. Is there a special way to do this?

Are future Pants version going to be compatible with Catalina too? Or is 2.12.0 is the last version for this OS?

Future Pants do all the way through 2.14.x: https://pypi.org/project/pantsbuild.pants/2.14.0.dev6/#files We will drop support at some point, but I'm not sure we've decided when yet. No earlier than 2.15.x though.

Hi guys, I am using pants behind a firewall and

./pants package

fails with following error:

15:55:08.93 [ERROR] 1 Exception encountered:

  Exception: Error downloading file: error sending request for url (<https://github.com/pantsbuild/pex/releases/download/v2.1.90/pex>): error trying to connect: invalid peer certificate contents: invalid peer certificate: UnknownIssuer

Is there a proxy setting that can be configured in Pants?

Ok, thanks!

Newbie question: when running

pants_from_source

to test changes, is interpreter constraint

==3.9.*

somehow added? I've been building with

==3.10.*

and its been working fine on 2.13 rc, but running from source is failing because of conflicting constraints

Hi folks! https://graphmyrepo.com/ is a new site we’ve created at Toolchain that we hope will be useful to software engineers such as yourself. It uses Pants to analyze public GitHub repositories and creates an interactive graph of the code’s structure and dependencies. The site currently supports Python, Go, Java and Scala codebases, and its purpose is to show Pants’s capabilities off to a wide audience. I’d really appreciate it if you could take a few minutes to try out the site and provide some feedback on the experience. We hope to launch this publicly very soon, so your thoughts would be appreciated! Thanks! ~ Benjy

anyone ever seen this error on an m1 mac (pants 2.12)?

No interpreter compatible with the requested constraints was found:

  A distribution for lxml could not be resolved for /Users/ashu/.pyenv/versions/3.9.10/bin/python3.9.
  Found 1 distribution for lxml that do not apply:
  1.) The wheel tags for lxml 4.9.1 are cp39-cp39-macosx_12_0_arm64 which do not match the supported tags of /Users/ashu/.pyenv/versions/3.9.10/bin/python3.9:
  cp39-cp39-macosx_10_16_arm64
  ... 724 more ...

this happens when doing

./pants run

Good morning guys, I am trying to build a

pex_binary()

target using

package

goal but it fails with following error:

(pants) [root@9a5752857756 pants-training]# ./pants package src/client:greeter_client
13:07:32.60 [ERROR] 1 Exception encountered:

 BinaryNotFoundError: Cannot find `unzip` on `['/bin', '/usr/bin', '/usr/local/bin']`. Please ensure that it is installed so that Pants can download the tools Pants needs to run.

(pants) [root@9a5752857756 pants-training]#

I have the unzip package in `/usr/bin/`:

(pants) [root@9a5752857756 pants-training]# ls -ltra /usr/bin/unzip
-rwxr-xr-x 2 root root 206728 Dec 16 2021 /usr/bin/unzip
(pants) [root@9a5752857756 pants-training]#

Could someone please help with this?

🚲 🏚️

StyleRequest

is used by

fmt

,

lint

,

check

, and soon-to-be-

fix

. Anyone wanna help me play the name game for a more appropriate name? Really it's just an association of tool name to field set 🤔

RunToolOnTargetRequestBase

?

Hi, I’m using pants 2.14.0dev2. We are trying to run tests in CI only for the changed projects.

pants --changed-since={COMMIT} --changed-dependees=transitive roots

I realised that roots ignores

--changed-since

and

--changed-dependees

, because it prints all the projects. But when you use:

pants --changed-since={COMMIT} --changed-dependees=transitive list

-> it shows all the targets. Our solution is to cut the project names and filter the output from the list, but is it expected somehow in the future to support

changed-since

and

changed-dependees

for

roots

command? Because I see it works for `lint`/`test` for example.

I am trying to build a Docker image for one of my sources and getting following error:

(pants) [root@9a5752857756 pants-training]# ./pants package src/server:docker
09:52:28.41 [INFO] Completed: Building dockerfile_parser.pex from dockerfile-parser_default.lock
09:52:32.72 [INFO] Completed: Building docker image docker:latest
09:52:32.73 [WARN] Docker build failed for `docker_image` src/server:docker. The src/server/Dockerfile have `COPY` instructions where the source files may not have been found in the Docker build context.

The following files were not found in the Docker build context:

  * ./3rdparty/requirements.txt
  * ./src/server/


09:52:32.73 [ERROR] 1 Exception encountered:

  ProcessExecutionFailure: Process 'Building docker image docker:latest' failed with exit code 1.
stdout:

stderr:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?



Use `--no-process-cleanup` to preserve process chroots for inspection.

(pants) [root@9a5752857756 pants-training]#

My source can be found here. It seems like I need to add some dependencies to the

docker_image()

target which I already tried but it did not work. Could anyone please help me with that?

What does the backend

pants.backend.experimental

signify? Does it mean the features provided by this backend are in “experimental” stage and may be removed in future?

Hi guys. I had a really basic question. I see a lot in the Pants documentation for how to run tests and lint in CI, but I don't see too much when it comes to actually deploying built assets. Is there any recommend way of doing this? Is there an easy way of doing this in a way that only detect changed assets?

I want to publish a wheel built using Pants to an internal hosting site. What changes are required in

pants.toml

?

Since

./pants run my_file.py

now runs the script in your workspace, should we elide add support for

./pants run my_script.sh

?

Hello. I have a monorepo with several projects and a single pipeline. I deploy stuff in the cloud. Right now, I use bash/python scripts to call pants and do the build and deployment. Each pipeline run deploys all projects all the time. I'd like to avoid that and instead deploy only the changed parts. I was wondering if I could use something like what the CI page describes for the lint/check/test goals. But I'm not sure what goal to use. The best would be something that tells me that my package targets need to be rebuilt because things have changed like for the

test

goal (which is different from building the packages because they don't exist on

dist/

). I was also wondering about the

publish

goal. That seems to be more to push artifacts on repositories like artifactory. Would it be a good practice to use

publish

to also deploy stuff on the cloud using CloudFormation or Terraform or Pants is not the right tool for that?

Where do I include a username and password for an image registry: www.pantsbuild.org/docs/tagging-docker-images#configuring-registries ?

What would occur such that a user would see the following when `./pants run`ning a Python source 🤔

...
"/home/firstnamelastname/.cache/pants/named_caches/pex_root/unzipped_pexes/00c6aeedd3e540664acb24335a35fdecfe180a56/.bootstrap/pex/hashing.py", line 180, in file_hash
    with open(path, "rb") as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/home/firstnamelastname/.cache/pants/named_caches/pex_root/venvs/00c6aeedd3e540664acb24335a35fdecfe180a56/b989780bc0156be1e5370338299e165b5396324b.b1aea9bdeda6439194d975734b2f252e/bin/spark-class'

I'm seeing errors attempting to load https://www.pantsbuild.org/, e.g.

Error 1016  Ray ID: 73f7b98a07ed5527 • 2022-08-23 23:45:56 UTC
Origin DNS error

A random internet is-it-down detector seems to agree that it's not working.

Just wanted to confirm if pants supports django v4 or not. Cuz I an getting error while generate lockfiles with this version.

stderr:
ERROR: Could not find a version that satisfies the requirement Django<5.0.0,>=4.1
ERROR: No matching distribution found for Django<5.0.0,>=4.1

Is it possible to create a single python (pex based) lock file with multiple versions of the same package? I have a small number of components that need to support a broad range of interpreter versions (going as low as 3.6), and it’s impossible to get all our 3rd party deps to support this far. I’ve had success isolating those components to their own resolve/lock-file, but I feel like I’m losing one of the core benefits of the monorepo since I now need to carefully self manage which resolve is used and which components share code. Is there a better way?