Hello dear Pants developers and happy New Year for those I did not interact with (yet) this year! 🥂 We upgraded from Pants 2.14 to Pants 2.15 at my client and a custom

bump

plugin we have written is now having hiccups with messages of the form:

Filesystem changed during run: retrying

Bump

in 500ms...

Because the

bump

task bumps version numbers in

pyproject.toml

files, the retry is causing multiple bumps to happen with one command. As in, we request bumping the patch number once, and

0.0.1

gets bumped to

0.0.3

or

0.0.4

. It's not deterministic and I did not yet understand the trigger 🤷 My question is: would

--no-watch-filesystem --no-pantsd

be a quick workaround until I figure things correctly?

Is there certain restriction on how much resource pants is allowed to use when running certain goal e.g. when running tests? I see quite a lot of OOM related exit code (-11) when running tests using pants locally on my laptop but not in our CI/CD

Am I reading https://github.com/pantsbuild/pants/issues/16602 right that today if I want some of my code to depend on the 3rd party python package

foo[bar]

, other code to depend on

foo[bar,bax]

and yet other code to depend on

foo[qux]

, then those dependencies need to be in separate resolvers?

anyone here have experience in putting together Pulumi and Pants?

Hi everyone, I'm new to Pants and am trying to learn / evaluate it for a potential project. One pattern we follow in the project is managing two separate requirement files

requirements.txt

and

requirements-dev.txt

. The first is for 3rd party dependencies we use in our application while the second is limited to

pytest

,

black

,

flake8

, and the like. When developing we have one

venv

that we can point VS Code . In addition to the code completion benefits we can use VS Code's Testing extension with python to easily set breakpoints when debugging tests. I ran

./pants export ::

but

pytest

isn't included as a dependency in the main

venv

it exported and I'm not sure how to use the exported

pytest

venv

as it's not able to import any of my code (I'm using a

src

style layout). I could just include

pytest

as a 3rd party dependency and specify

export = false

in my

pants.toml

but I don't want to ship

pytest

to production. How can I setup Pants so I can maintain install dependencies (e.g. pytest, typeshed, etc) to facilitate a good developer experience while ensuring I don't ship dev dependencies to production?

If there are any French here 🇫🇷 , you can come meet me when I will speak about my experience introducing Pants at kaiko.ai during the PyConFR conference (in Bordeaux on February 18th) 👋🏻 Disclaimer: everything will be in French I believe 😇 cc @busy-vase-39202

two offhand bits of low context feedback: • it’s awesome to be able to say “with python <version> (I like

asdf

over

pyenv

but either once set up make that easy), just do `./pants run x`” and skip any conversation about venvs when onboarding a non-python colleague to a codebase •

./pants repl ::

with ipython set in the config is really great

and a probably-simple question -

11:11:33.65 [WARN] Pants cannot infer owners for the following imports in the target <..>/stepfn.py:

  * mypy_boto3_stepfunctions.client.SFNClient (line: 7)

I’m using type stubs mapping here, which makes mypy happy but still emits the above warning - but I can’t also use

module_mapping

- how should I avoid that warning? Everything works at runtime, but I’d rather not go and comment each import line if there’s a better way 🙂

type_stubs_module_mapping={
        "boto3-stubs": ["boto3"],
    },

Hey, I am trying to run my tests in a docker environment.

docker_environment(
    name="dev_docker",
    platform="linux_x86_64",
    image="test", # python:3.10.4-slim-bullseye docker image
    python_bootstrap_search_path=["<PATH>"]
)

On the test I have set the environment

python_tests(
    name="tests",
    environment="dev_docker"
)

When I now try to run that test I get the following FileNotFoundError:

./pants test ::
13:06:26.16 [ERROR] 1 Exception encountered:

Engine traceback:
  in `test` goal

ProcessExecutionFailure: Process 'Find interpreter for constraints: CPython>=3.10.*' failed with exit code 1.
stdout:

stderr:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 189, in _run_module_as_main
    mod_name, mod_spec, code = _get_main_module_details(_Error)
  File "/usr/local/lib/python3.10/runpy.py", line 223, in _get_main_module_details
    return _get_module_details(main_name)
  File "/usr/local/lib/python3.10/runpy.py", line 129, in _get_module_details
    spec = importlib.util.find_spec(mod_name)
  File "/usr/local/lib/python3.10/importlib/util.py", line 103, in find_spec
    return _find_spec(fullname, parent_path)
  File "<frozen importlib._bootstrap>", line 945, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1439, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1411, in _get_spec
  File "<frozen zipimport>", line 170, in find_spec
  File "<frozen importlib._bootstrap>", line 431, in spec_from_loader
  File "<frozen importlib._bootstrap_external>", line 741, in spec_from_file_location
  File "<frozen zipimport>", line 229, in get_filename
  File "<frozen zipimport>", line 752, in _get_module_code
  File "<frozen zipimport>", line 586, in _get_data
FileNotFoundError: [Errno 2] No such file or directory: '/pants-sandbox/pants-sandbox-kEtOGg/./pex'

Does anyone know what the problem might be?

how would I tell regex-lint (https://www.pantsbuild.org/v2.15/docs/reference-regex-lint) to skip a particular file or directory ? I don't see anything in the docs... We are using it targetless, do I need to add a BUILD file w/ a target and set the skip flag there somehow ?

hitting an odd pypi/pex building error today a lot:

ERROR: Could not find a version that satisfies the requirement pantsbuild.pants.testutil<2.15,>=2.14.0a0
ERROR: No matching distribution found for pantsbuild.pants.testutil<2.15,>=2.14.0a0

seems like there are definitely distributions that match that

I'm trying to depend on helm artifact in a private (username/password) registry. I haven't been able to figure out how to do this from the docs, but I see there is support for publishing https://www.pantsbuild.org/docs/helm-overview#configuring-oci-registries helm artifacts. I presume helm registries require authentication to write to, so I'm not sure what helm authentication config I'm missing.

Is there work planned to obviate the need for setting PANTS_CONCURRENT=True in order to run two commands at the same time? Ideally without a performance penalty. I ask because we are starting to roll out pants usage to more of our org, and we are faced with either the annoyance of never running two commands at the same time, or significant performance degradation (for short commands it can be 10x slower to set PANTS_CONCURRENT=True). I don't know enough about pants internals to know how crazy an idea this is, but it would have a big impact on our team.

Bit confused about the docs regarding

pants.ci.toml

Then, in your CI script or config, set the environment variable

PANTS_CONFIG_FILES=pants.ci.toml

to use this new config file, in addition to

pants.toml

.

In my testing, i seem to need to specify

PANTS_CONFIG_FILES="['pants.toml', 'pants.ci.toml']"

for the options to get merged

Hello, I'm playing with Pants, I'm trying to build docker image that include a basic python script that depends on 3rd party library. I've choose

pydantic

library. I'm building locally PEX with the following snippet in the BUILD and it is running fine on my laptop:

pex_binary(
    name="pydantic-cli",
    entry_point="main.py",
    dependencies=[
        "projects/py/project_2:poetry#pydantic",
    ]
)

Now I'm trying to pack this PEX into the Docker, so I've added the following snippet to the BUILD

docker_image(
    name="pydantic-cli-docker",
    dependencies=[
        ":pydantic-cli",
    ]
)

I'm able to

pack

the docker image, but when I'm running the container it fails:

Failed to find compatible interpreter on path /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin.

Examined the following interpreters:
1.) /usr/local/bin/python3.9 CPython==3.9.16

No interpreter compatible with the requested constraints was found:

  A distribution for pydantic could not be resolved for /usr/local/bin/python3.9.
  Found 2 distributions for pydantic that do not apply:
  1.) The wheel tags for pydantic 1.10.4 are cp39-cp39-macosx_10_9_x86_64 which do not match the supported tags of /usr/local/bin/python3.9:
  cp39-cp39-manylinux_2_28_aarch64
  ... 304 more ...
  2.) The wheel tags for pydantic 1.10.4 are cp39-cp39-macosx_11_0_arm64 which do not match the supported tags of /usr/local/bin/python3.9:
  cp39-cp39-manylinux_2_28_aarch64
  ... 304 more ...

Now

pydantic

is coming with pre-compiled binaries in the wheel, but for some reason it finds them incompatible. Note: My laptop is M1 Macbook I would like to be able to debug such scenarios alone, but I'm not sure where to start here, please advise.

Hello, I'm in the process of setting up a new Python monorepo that will contain internal libraries and AWS Lambda functions. I wasn't aware of Pants when I started, so my current implementation is using Poetry to manage dependencies. Reading the docs on integrating Pants with Poetry, I get the impression that the whole reason for Poetry support is to make it easier for existing Poetry-based projects to migrate to Pants. Given that I'm starting fresh, is the recommended approach to just use Pants without Poetry? I'm not sure if Poetry provides useful features that Pants does not.

Is there a way to to generate a pex of a python tool managed by pants? For example, rather than exporting like

pants export --resolve=pylint

and getting a venv, is there a way to get a pex instead?

Possibly related to above (not sure), is there a way to pre-build test pex files? I have a project whose tests need to be run in serial (making them parallelizable is a sizable work in progress) so I’m using

--process-execution-local-parallelism=1

. That causes building requirements.pex, pytest.pex, etc to be done in serial and I would like to parallelize this first part then run the tests in serial

do import statements not work in .proto files? i can’t get pants to see interdependent protobuf files

Hello everybody. I got a mono-repo for libraries where each library is to be publish individually (as got different legacy consumers). They are all configured with poetry and I would love if I can implement individual versioning by using

poetry version xxx

(patch, minor, major). So each publish library has its own cadence depending on the changes. I don’t see anything option in pants to allow versioning (specially individually) but I might be missing something. Is this, or another similar option, supported? As an alternative, I was thinking it might just be ok to add a macro that runs just before the package state (but only if the system has detected changes). Having an individual version and increasing the version number for all packages is also an option, but that means we deploy all libraries all the time (even if there aren’t changes) what ain’t ideal. Other options/ideas welcomed! Thanks in advance!

Hi! I was looking to get some help on understanding how to easily set

resolve

for a bunch of

python_sources

calls. I have a repo with a couple different projects which have conflicting numpy version dependencies among other things. Based on this guide I was able to setup different resolves and set those resolves for the

python_requirements

calls that I have for these projects. However, when trying to setup the resolves for my

python_sources

, I am having to add

resolve="something"

to a bunch of different

BUILD

files since I have a bunch of subdirectories within the project. I was wondering if there is an easy way to ask

pants

to consider the same resolve for all

BUILD

files within a subdirectory so I can just keep

python_sources()

in my BUILD files for these subdirectories. Hopefully this makes sense, definitely let me know if I am misunderstanding anything here. Thanks!

Just want to confirm if this is a typo?

.pantd.d/pants.log -> .pants.d/pants.log

on the last version of https://www.pantsbuild.org/v2.15/docs/using-pants-in-ci#tip-store-pants-logs-as-artifacts

trying to run pants in my CI (tests work fine locally) and got stuck when CI is building stuff:

Building 47 requirements for requirements.pex from the thirdparty/python/default.lock resolve: alembic==1.4.3

is taking forever. any docs/tips on ci integrations? All I am running is

./pants test ::

I know I've been opening many tickets on experimental backends and asking questions here. Thanks 👖 team for all of the tantalizing capabilities on the horizon!

I'm working on a goal to run security auditing tools. Since the result will always be dependent on the state of the outside world (the currently reported vulnerabilities) I need to make sure we never cache the result. Is there a preferred way to mark a goal/result as uncachable?

Does anyone have any public real world examples of a pants repo that is building python, and c++ or rust ? I understand c++/rust would be via shell but visible examples would be good

I am having trouble with the

export

goal that I can't seem to figure out. Earlier today I deleted my local pants caches and now when I run

./pants export --resolve=default

the symlink in the dist directory links to a non-existent directory in ~/.caches. Running

./pants export ::

to export all resolves does not seem to have this problem.

Hi everyone, it's nice to join the community! I'm exploring using pants as an alternative to bazel for managing our python and js monorepo. Wanted to get your help on making the decision, mainly by getting more understanding of the following questions - 1. Is there support for hermetic python? I would not want to rely on local installation of python (not for dev and not for deployment) 2. We have a use case where we build a python server and embed it inside a js application. How would that work with pants? 3. Cross platform. We work on both macos and linux. Is there support for this with pants? Can we build dockers from macos?

Hi all. I am getting an error testing out docker functionality.

#3 [internal] load metadata for <http://docker.io/library/python:3.8|docker.io/library/python:3.8>
#3 sha256:edad251955f644c6004999f0af04035912392fa02db26821676452becbc715fb
[2023-01-28T15:31:23.094439000Z][docker-credential-desktop][F] get system info: exit status 127
[goroutine 1 [running, locked to thread]:
[common/pkg/system.init.0()
[       common/pkg/system/os_info.go:32 +0x29d
#3 ERROR: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: ``
------
 > [internal] load metadata for <http://docker.io/library/python:3.8|docker.io/library/python:3.8>:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: ``

I have some tests that use globs to access other directories of files, so I’m adding a dependency from the tests to a new

target()

with dependencies on the subdirs. That should ensure the glob is satisfied for the tests. Here is the directory and the

target()

I’m adding for it: https://github.com/StackStorm/st2/tree/master/st2tests/st2tests/fixtures/packs https://github.com/StackStorm/st2/pull/5874/files#diff-0a765a0e1409bcce280bee085bd5903e219b4c63a442696f8d23216a525d882a But, I am afraid (and I’ve got feedback from others who are afraid) of not keeping the

target()

dependencies up-to-date as people add new directories. Can I use globs in

dependencies

to avoid that? And if yes, can I use

!

to ignore a couple of directories so they are not direct dependencies (but transitive is fine)?