Is there a recommended way to skip lint checks for BUILD macro definition files? If I define a

python_sources()

for my BUILD macro, then flake8 complains that it can't resolve the target names, but these are dynamically defined by Pants and can't be imported. I'd rather not sprinkle flake8 ignores, but I'm not sure what the normal way of handling this is

Is there a way to see the generated

setup.py

file from the

python_distribution

target? I tried

--keep-sandboxes=always

but nothing I saw had the

setup.py

in it. I’m just experimenting with some changes and it’d be easier to inspect the file than rebuild and reinstall

I’m seeing the “Unmatched Glob” problem in my project, but the files its referring to were deleted a while back. Is there some sort of caching mechanism that means it’s still looking for these files? I ran

./pants tailor ::

as well as

./pants generate-lockfiles

but it’s still there.

14:41:38.91 [WARN] Unmatched globs from src/wanpan/extraction:extraction's `sources` field: ["src/wanpan/extraction/*.py", "src/wanpan/extraction/*.pyi"], excludes: ["src/wanpan/extraction/*_test.py", "src/wanpan/extraction/*_test.pyi", "src/wanpan/extraction/conftest.py", "src/wanpan/extraction/test_*.py", "src/wanpan/extraction/test_*.pyi", "src/wanpan/extraction/tests.py", "src/wanpan/extraction/tests.pyi"]

Do the file(s) exist? If so, check if the file(s) are in your `.gitignore` or the global `pants_ignore` option, which may result in Pants not being able to see the file(s) even though they exist on disk. Refer to <https://www.pantsbuild.org/v2.14/docs/troubleshooting#pants-cannot-find-a-file-in-your-project>.

The BUILD file at that location doesn’t even have

extraction

as a target:

python_sources()

shell_sources(
    name="launch_ec2_extraction",
)

Hi guys, I'm finding pants hangs on the

Building manage.pex with...

step, but I'm not getting any logging to figure out which package is causing the issue. Is there any way to enable logging for this?

Is there any way for pex to make a lockfile on a mac (amd64) targeting linux given a requirement

pyinotify==0.9.6; platform_system == "Linux"

? Looks like the setup.py is poisoned, so this would require some kind of “spoofing” to make

setup.py egg_info

succeed: https://github.com/seb-m/pyinotify/blob/master/setup.py#L27-L30

WARNING: Discarding <https://files.pythonhosted.org/packages/e3/c0/fd5b18dde17c1249658521f69598f3252f11d9d7a980c5be8619970646e1/pyinotify-0.9.6.tar.gz#sha256=9c998a5d7606ca835065cdabc013ae6c66eb9ea76a00a1e3bc6e0cfe2b4f71f4> (from <https://pypi.org/simple/pyinotify/>). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
ERROR: Could not find a version that satisfies the requirement pyinotify==0.9.6
ERROR: No matching distribution found for pyinotify==0.9.6

Does pants have any mechanism for selecting resolve for specific dependency at call-time, CLI, or something local? Or "enforce" a specific resolve for a library from different binary targets? We use

torch

in multiple of our repos; and based on hardware and other specifications we need to switch which "flavor", which is done using localtags:

+rocm

or

+cuNNN

for GPU backends,

+cpu

for "CPU-only", or nothing. I've managed to get a bunch of different resolves to work, but I'm not sure how to tie this into dependency inference for local execution, nevermind trying to publish anything using this abomination of version management.

Hi all, I am trying to use the debugger (with vs code) in our python project. We set up our codebase with the <https://www.pantsbuild.org/docs/source-roots#srclang-setup%7Csrc/&lt;lang> setup> as instructed in the docs. It works very well. However, when I want to debug my code, it never stops on the breakpoint. I am thinking that path mappings are incorrect but really couldn’t find a solution. Here is the repo for demonstration: https://github.com/aeroith/example-python

Just wondering, for tools that generate reports (coverage-py, mypy, etc.) by aggregating individual result files of selected targets, is there a way to define subsets of the targets for which to generate these reports? The point is to both feed as many targets to Pants at once to take advantage of the execution engine, and also generate aggregated reports with sensible target scope. For example, when testing two independent projects simultaneously, it's easy to identify and relocate the individual test result files in ./dist/test/reports, but the coverage report in ./dist/coverage/python will have both project's tests results in it, so a copy must be made and relocated for each individual project, and this will be confusing to an outside reviewer who will wonder why project Y is in project X's coverage report.

Hello, I have a non-public dependency that is not published on PyPi that has an overlapping name with a package on PyPi. Further, it is a C extension and compiled against a particular version of Python. I need to specify the specific index this package comes from, but only for this package, and it must ignore the pypi name conflict. Is there a way to do this?

Hi I have a question about VCS-style requirements. A bit confused on this part of the docs how and where do i specify these requirements? it seems like

python_requirement

expects only a pip-requirement string eg.

setuptools==65.5.0

and doesn't parse something like

'git+<https://github.com/facebookresearch/pytorch3d.git@stable>'

I'm having a weird issue with lockfile generation and verification w.r.t.

python_requirement

. We have some requirements on

boto===2.49.0a1

. I believe this is an internal boto fork that only exists in our private artifactory. However, lockfile generation turns this into

boto===2.49a1

which then fails all the

python_requirement

constraints. Changing the lockfile manually to

boto===2.49.0a1

doesn't fix it either. Is the version number ill-formed or something?

Has anyone tried to integrate Voila into a Pants-based project? We're using it to serve a notebook-based app. I think the problems I'm having are pretty basic, but I would appreciate a second set of eyes if anyone has any ideas! Details in 🧵

It seems

pex

does not honor

indexes.add

after the first entry 😞

I just added a source root configuration so I could add some type stubs. My

pants.toml

now contains:

[source]
# Add typings as a source root so I can put type stubs in there.
root_patterns = ["src", "typings"]

other than that, it is unchanged.

./pants test

,

check

,

lint

, etc. work as expected but

package

does not:

$ ./pants package ::
15:24:49.37 [ERROR] 1 Exception encountered:

  NoSourceRootError: No source root found for `.`. See <https://www.pantsbuild.org/v2.13/docs/source-roots> for how to define source roots.

For reference:

$ ./pants roots
src
typings

That config replaces your old source roots, did you mean

root_patterns.add =

?

@happy-kitchen-89482 I think I want to replace my old source roots, right? I only have 2:

src

and

typings

...

Just checking

Yeah, that makes sense, but it looks like you have something at the repo root that Pants thinks needs to be under a source root

Hence the

NoSourceRootError: No source root found for .

Try adding

/

to the source roots, to see what happens

I do have a

BUILD

file there with things like

python_requirements(module_mapping=...)

yup, that did the trick. I assume the

BUILD

in the root is the right thing to do, right?

If that’s where your requirements.txt file is, then yes

What else do you have in that BUILD file?

(Y'all wanna move to thread @happy-kitchen-89482 @plain-carpet-73994 🙂 )

Is there any reliable metric for detemining when a pants command line command is "done"? In the shell completions, if I want to show directories, files, AND completions - it ends up looking like this mess. Hard to tell what's a goal, and what's an extensionless file.

3rdparty/                                 build-support/                            experimental-deploy                       internal-generate-test-lockfile-fixtures  peek                                      test
BUILD                                     cargo*                                    experimental-explorer                     java-dump-source-analysis                 publish                                   test.sh
BUILD_ROOT                                check                                     export                                    jvm-symbol-map                            py-constraints                            testprojects/
CODE_OF_CONDUCT.md                        check-default-tools                       export-codegen                            lint                                      pyproject.toml                            tests/
CONTRIBUTING.md                           completions                               filedeps                                  list                                      repl                                      update-build-files
CONTRIBUTORS.md                           conftest.py                               filter                                    package                                   roots                                     version
LICENSE                                   count-loc                                 fmt                                       pants*                                    run                                       
MAINTAINERS.md                            dependees                                 generate-lockfiles                        pants-plugins/                            rust-toolchain                            
README.md                                 dependencies                              help                                      pants.ci.toml                             scala-dump-source-analysis                
auth-acquire                              docs/                                     help-advanced                             pants.toml                                src/                                      
auth-token-info                           experimental-bsp                          help-all                                  paths                                     tailor

Gets a bit better when narrowing, but still 🤷

% ./pants t
tailor         test           test.sh        testprojects/  tests/

Hi all, I'm looking to introduce BDD to our monorepo, and wonder how much work it will be to use

behave

for testing BDDs. I would just need to invoke

behave

instead of

pytest

and maybe tweak some args here and there.

Hi, I’m trying to setup Pants in an existing monorepo. We have a use-case which I’m not sure is handled correctly by pants: 1. We have multiple repos, one of which is a mono-repo. 2. In repo A (not not a mono-repo), we produce a package called

internal.db

(where

internal

is a namespace package). 3. In repo B (which is the mono-repo where I try to integrate Pants)

internal.db

is in use and other packages under the

internal

namespace are produced. I think there is a conflict since

internal

is partially defined inside the mono-repo and partially outside. The error I get is of the following form (I get lots of them and they come in pairs:

15:44:04.72 [WARN] The target internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources imports `internal.db`, but Pants cannot safely infer a dependency because more than one target owns this module, so it is ambiguous which to use: ['//:root#internal-db', 'internal_analytics/internal/__init__.py:../internal-analytics-src-sources', 'internal_athena/internal/__init__.py:../internal-athena-src-sources', 'internal_data_science/internal/__init__.py:../internal-data-science-src-sources', 'internal_logs/internal/__init__.py:../internal-logs-src-sources', ..., 'internal_sqs/internal/__init__.py:../internal-sqs-src-sources'].

Please explicitly include the dependency you want in the `dependencies` field of internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources, or ignore the ones you do not want by prefixing with `!` or `!!` so that one or no targets are left.

Alternatively, you can remove the ambiguity by deleting/changing some of the targets so that only 1 target owns this module. Refer to <https://www.pantsbuild.org/v2.14/docs/troubleshooting#import-errors-and-missing-dependencies>.
15:44:04.72 [WARN] Pants cannot infer owners for the following imports in the target internal_backoffice/internal/backoffice/__init__.py:../../internal-backoffice-src-sources:

  * internal.db (line: 11)

I’ve tried adding the follwing to the root

BUILD

file but it didn’t fix it:

__defaults__({
  python_requirements: {
    "module_mapping": {
      "internal-db": ["internal.db"],
    }
  }
})

And

internal-db

is in Pants’ req file. I’ll try to setup a repro, but not sure when I’ll be able to…

Hi! I might need to setup a remote cache, and unfortunately it has to be self-hosted. I see the docs are recommending three such applications, but I have no experience with this and don't know which to choose. I can't fins comparisons between them, so I would like to ask if anyone could recommend one or another. I suppose the requirements are "it should work" and "it should be easy to setup" :-)

Is there any kind of introspection command that can be used to extract configuration values from

pants.toml

, particularly default ones that haven't been explicitly set or overridden? In particular, I'm looking to programmatically find out the currently-configured

protoc

version (https://www.pantsbuild.org/docs/reference-protoc#version). I know I can set a value concretely and then just process the TOML myself, but I was wondering if Pants already had some built-in capabilities along these lines. Thanks! 🙏