When running our integration tests (AWS using boto3) we have to enter our MFA code many times, I'm assuming this is because of the multiprocessing/multithreading ? Is there a way to cache these for use across all tests?

Does the Go backend support

extra_env_vars

? I have

[test]
extra_env_vars = ["VAR=value"]

in

pants.toml

This works in Python, but those environment is completely empty for Go?

Has anyone gotten pants to work on Alpine Linux yet? If not, is it possible?

Can someone explain what a “dedicated build server” is and how it differs from traditional CI pipelines like Jenkins/Gitlab?

Is there an alternative to traditional CI that is possible with Pants?

Hello guys, I am looking for a toy example of utilisation pants with Poetry. I have read already all messages here with key a word ‘poetry’. My case is really simple, there is a mono repo, where I want to build two libs (A and B), so that B depends of A and shares the same namespace. Could you share please any examples for inspiration?

trying to upgrade our version of

black

and i’m getting an error i don’t understand when trying to run

./pants fmt

, does anyone understand what the issue is? (traceback in thread)

How can I add a file to the docker context that is located in the root of my repo, e.g.

entrypoint.sh
pants.toml
/serviceA
    Dockerfile
    BUILD

And the COPY in the Dockerfile looks like this:

COPY entrypoint.sh /

What needs to be added to the BUILD file? It is always complaining that the file cannot be found.

I'm seeing very high startup times on a certain docker image, which happens to be running a PEX binary thats ~1.5GB in size and contains at least 1 GB worth of a dir containing 100k files. Any tips on making this less more startup-friendly? 🙂

just saw that pants 2.12 was released today! 🚀 are there any plugin upgrade notes for 2.12? we’re just about finished upgrading to 2.11, but we might just include the jump to 2.12 as well https://www.pantsbuild.org/docs/plugin-upgrade-guide

not 100% sure what’s causing this, but running

./pants fmt ::

is printing out multiple lines for some reason (see thread)

Is there a way to just pass all environment variables to a test? https://www.pantsbuild.org/docs/python-test-goal#setting-environment-variables Aside the fact that it seems not recommended

Hi, I don't think this is a pants issue but would like some suggestion on how to handle this. I am using pants in our

pre-commit

for linting formatting. I added a flake8 plugin called

flake8-docstrings

to check for docstring. In case the lint check for flake8 fails because of docstring, pre-commit doesn't show any log about what are the checks its failing. On the other hand, when I manually run

./pants lint ::

I do see the log about what are the cases which are failing. This is how the

.pre-commit-config.yaml

section looks like

- repo: local
  hooks:
    - id: lint-check
      name: Checking source files formatting
      entry: "./pants --changed-since=main lint"
      language: script
      types: [python]
      pass_filenames: false
      verbose: true

Protobuf/grpc integration with Pants 2.12.0 question 🧵

hey folks, I'm having a weirdness with lockfiles. when trying to install

msal-extensions

, it has a dependency on portalocker, which has a dependency on

pywin32

on windows. If I have

msal-extensions

listed directly in a

python_requirment

, it thinks that it always needs

pywin32

. But if instead I copy the dependencies that it requests, it correctly identifies that it only needs

pywin32

on windows. Details and repro in thread

Hi, I am testing the --debug-adapter feature with test and run goal. I am getting the following warning: `[WARN] Using

run --debug-adapter

on the target django:manage, which sets the field

run_in_sandbox

to

True

. This will likely cause your breakpoints to not be hit, as your code will be run under the sandbox's path.` My breakpoints do not work when debugging tests or debugging a normal run. Is there a way to make that work? Currently I am using PANTS_SHA: 918ac2f68182a8d308113eff336f55dcdbc84847

Has anyone had issues with help working in

pants repl

? E.g.,

help(str)

in

repl

gives me empty output.

Looking at 2.13.0a1, I see: https://github.com/pantsbuild/pants/pull/15534 which removed the undocumented

!

. That only applies to CLI specs, right? We aren't replacing

!

specs in BUILD files with

-

right?

👋 — hello, new to pants build — pretty excited about a tool that may just deliver on the promise of bazel tooling without all the awkwardness of starlark and WORKSPACE woes 😆 … i was surprised to not find any general/core handling of external repositories though — is that uncommon with pants? something for vendoring third party code via either remote archives, or git repositories, without having to resort to a custom plugin to provide something to get started?

Hey all, I’m hoping for some advice re: the new resolves feature. I’m a huge fan, and it will be very useful for us, but I’m running into issues. Our monorepo has a common python_sources target called

src/common:lib

which depends on some 3rd-party python packages, and many other modules which each have their own additional 3rd party dependencies. These other modules follow a pattern of

python_requirements

->

python_sources

->

pex_binary

->

docker_image

->

python_tests

. Their

python_sources

all declare a dependency on

src/common:lib

. My intention is to have all the dependent modules inherit the python dependencies of

src/common:lib

, but I can’t do that without multiple resolves. When I try that, I get errors trying to reference those targets. Example:

python_requirements(resolve="align")

python_sources(
    name="lib",
    sources=["src/*.py"],
    dependencies=[
        'src/common:lib',
        '#pandas',
        '#pysam'
    ],
    resolve=parametrize("align", "common")
)


pex_binary(
    name="exe",
    entry_point="src/align.py",
    dependencies=[':lib'],
    shebang="/usr/bin/env python3",
    platforms=[
        "current",
        "manylinux2014_x86_64-cp-39-cp39",
    ],
    resolve=parametrize("align", "common")
)


docker_image(
    name="docker",
    image_tags=["{build_args.GIT_BRANCH}", "{build_args.GIT_COMMIT}", "{build_args.RELEASE_VERSION}"],
    dependencies=[
        "src/common/docker:python_base",
        ":exe",
    ]
)


python_tests(
    name="tests",
    sources=["tests/test_*.py"],
    dependencies=[
        ":lib",
        "src/test_framework:lib",
        ":test_data",
    ],
    runtime_package_dependencies=[":docker_test"],
    tags=["docker_required"],
    resolve=parametrize("align", "common")
)

When I test this, I get:

ValueError: The address `src/stages/align:exe` was not generated by the target `src/stages/align:exe`, which only generated these addresses:

  * src/stages/align:exe@resolve=align
  * src/stages/align:exe@resolve=common

Did you mean to use one of those addresses?

Any idea how to work with this? I tried setting the

:exe

targets to

:exe@resolve=align

and

:exe@resolve=common

, and even tried both at once - but each time they errored out because neither resolve has the full set of dependencies.

Hey folks, what's a good way to get pants to add a dependency even if it looks unused? The Azure async libraries need aiohttp installed, but it's imported somewhere deep and it looks like Pants isn't including it in the pex

How are the folder names of the

unzipped_pexes

determined?

I'm looking at building a micropython plugin for Pants (Because it's yet another hostile python runtime and I seem to gravitate towards them?) Micropython comes with a low-budget

pip

implementation (https://github.com/micropython/micropython/blob/4b9a2abbdec0e905fbc08f247513e43fb6bff39e/tools/upip.py) that installs packages to a directory for you. But it's uh, low-budget, and has some issues. But the main thing it does is puts the code where it's needed (in micropython your

PYTHONPATH

is

/

and that's where you put everything.) Can I do this with pant's existing pex packaging? Just need the .py files copied to a directory.

Hi, does pants support dependencies on local packages defined inside

pyprojec.toml

when using poetry?

Hi, using pants with python. For

python_sources

https://www.pantsbuild.org/docs/reference-python_sources In the docs under

dependencies

it says:

This augments any dependencies inferred by Pants, such as by analyzing your imports

Is there a way to disable the automatic import analysis and just use the manual list? I want to be explicit about the dependencies that’s all.

Hi, using pants with python (2). Is there a way when running

pants export

to skip the export of the virtualenvs for the tools (e.g.

pytest

,

autoflake

,

black

etc.) I only want to export the

python-default

resolve virtual-env. I see

export

has no options. https://www.pantsbuild.org/docs/reference-export Maybe I’m missing something though.

This is the closest I found: https://pantsbuild.slack.com/archives/C046T6T9U/p1655326716458969

There's a export option per tool you can set to false.

@bitter-ability-32190 may pick a link to the docs, I'm on the phone ;)