by any change is there a pants doc that outlines how to migrate from pants v1 to pants v2 for python ? We are manually trying to setup the v2 BUILD file for our python target . The one thing that is unclear is how to replace

python_library

goal ( which includes a

provides=setup_py

) in v2. Seems like

python_library

has been replaced with

python_sources

and if you want to specify distribution config then you add the

python_distribution

goal too in the BUILD file ? Is that correct ?

I have a collect_ignore_glob callout in my

conftest.py

to not run modules called

*_manual_test.py

. I know my

conftest.py

is getting picked up properly because I can see it with

./pants dependencies

calls. Are there any special things to get conftest to apply other than making sure it's a dependency like that? The docs make it seem like it should just work ™️ after that.

Is there a specific backend I have to turn on to have tailor recognize .txt or .json files as resources? Or do I need to manually add buildfiles for those?

This will probably sound bad without context, but is there any way to add a directory as a dependency recursively? I've got a bunch of

protobuf_sources

scattered under a tree and I need to bring them all in as a dependency for a

python_source

.

Is this a known issue? If I run

./pants help … | less

and then exit it with

ctrl-c

I get a

BrokenPipe

error (nothing strange about that) but the terminal is broken after that. (no echo etc..) (using

bash

on Mac)

I'm on version 2.7.1 ... How would I go about launching my pex binary with debugpy debugging?

I set

[python].interpreter_constraints

to CPython>=2.7,<3 and pants instructed me to generate a new lockfile for pytest. Running

/v2pants generate-lockfiles --resolve=pytest

fails on what looks like a py2/3 compatibility error in parsing python imports.

ProcessExecutionFailure: Process 'Determine Python imports for src/python/fsluigi/main.py' failed with exit code 1.
stdout:

stderr:
Traceback (most recent call last):
  File "./__parse_python_imports.py", line 114, in <module>
    main(sys.argv[1])
  File "./__parse_python_imports.py", line 105, in main
    visitor.visit(tree)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 249, in generic_visit
    self.visit(item)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 249, in generic_visit
    self.visit(item)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 249, in generic_visit
    self.visit(item)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 249, in generic_visit
    self.visit(item)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 251, in generic_visit
    self.visit(value)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 241, in visit
    return visitor(node)
  File "./__parse_python_imports.py", line 57, in visit_Call
    elif isinstance(node.args[0], ast.Constant):
AttributeError: 'module' object has no attribute 'Constant'

I am having trouble with bootstrapping that I can't quite figure out. When running any pants command I get an error with pex 2.1.42:

$ p list ::
Bootstrapping Pants using /Users/ryan.king/.asdf/shims/python3.8
Creating the virtualenv PEX.
Downloading the Pex PEX.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   640  100   640    0     0    870      0 --:--:-- --:--:-- --:--:--   876
100 3529k  100 3529k    0     0  2633k      0  0:00:01  0:00:01 --:--:-- 18.5M
No version is set for command python3.8
Consider adding one of the following versions in your config file at 
python 3.8.12
SHA256 of <https://github.com/pantsbuild/pex/releases/download/v2.1.42/pex> is not as expected. Aborting.

Adding config to upgrade doesn't seem to help

diff --git a/pants.toml b/pants.toml
index bb0945af39..8758c5189b 100644
--- a/pants.toml
+++ b/pants.toml
@@ -147,3 +147,6 @@ build_args = [
 config = ".pylintrc"
 source_plugins = ["//src/clr_pylint_checkers"]
 lockfile = ".pylint.lockfile"
+
+[download-pex-bin]
+version = "2.1.63"`

For context I both recently upgrade to Mac OS Monterey and we upgraded pants to 2.9.0

Hopefully easy one: I have

import requests

in my module and the

dependencies

goal is not showing in the output. I know it's in my

requirements.txt

and shows up in my

constraints.txt

as expected (specifically

requests==2.27.1

). I didn't see anything obvious in troubleshooting that was applicable. Any thoughts?

Example requirements.txt requested: --- I'm stress testing a new lockfile generation feature in Pex that Pants will be using as a first major customer and I'd like your help. The Python package ecosystem is pretty wild! See here and here for some pretty funky things I've already run across and handled. Pex strives to handle the Python packaging ecosystem in its entirety since its not fun to have someone else's problems affect your project / workflow / day. If any of you can provide requirements files that you think might be hairy and that just use PyPI, please attach them here and I'll see if Pex can handle locking them. Thanks in advance!

hi, just trying to update to

2.9.0

and im getting a dependency conflict with

docker-compose

over the pyyaml version i created a new venv to clarify the problem - and doing

pip install pantsbuild.pants==2.9.0 docker-compose

results in

ERROR: ResolutionImpossible: for help visit <https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies>

python==3.9.2, pip==20.3.4

hello! there is still time to vote in the 2022 roadmapping: take a few minutes to score the potential priorities if you haven’t yet! https://pantsbuild.slack.com/archives/C18RRR4JK/p1642626085023200

https://monorepo.tools/ <- Would be great for pants to be in there

Why does the "Resolving plugins" work appear to happen twice on pantsd startup?

statler-2:[~/src/pants][main]$ ./pants test src/python/pants/base/::
12:50:44.89 [INFO] Starting: Resolving plugins: hdrhistogram, toolchain.pants.plugin==0.17.0
12:50:49.77 [INFO] Completed: Resolving plugins: hdrhistogram, toolchain.pants.plugin==0.17.0
12:50:51.96 [INFO] Initializing scheduler...
12:50:53.10 [INFO] Scheduler initialized.
12:50:53.12 [INFO] Starting: Resolving plugins: hdrhistogram, toolchain.pants.plugin==0.17.0
12:50:56.64 [INFO] Completed: Resolving plugins: hdrhistogram, toolchain.pants.plugin==0.17.0

What's the simplest way with pants to answer "have any dependencies of this target changed?"? Context: In some of our CI jobs want to run goals based on all depenencies that have changed, but there are a few special cases where we want to invert the logic and say "for this given target, have any of its dependencies changed?".

is anybody using pants with a golang mono repo, or should i avoid it until it comes out of experimental stage?

I'm attempting to upgrade from scala 2.12 to 2.13. Continuing in a thread…

I can use

./pants export ::

to create a venv (for my IDE), but this doesn’t include extra_requirements for e.g. pytest. Is there a way i can get those exported as well?

Pants team invites you to add your organization or company to the Who Uses Pants page. We'd love to feature your team on this page! It helps showcase the diverse set of organizations that Pants is helping, and it demonstrates to your own users, employees and candidates that you're on the cutting-edge of the latest and greatest in build system technology. Click here to get started.

is it normal for the

pantsv2

test

goal to run on

__init__.py

files in the test target ? If so, has anyone encountered situations where it will fail , even though they are empty files ? Tried running with debug logs but nothing meaningful is shown other than the exit code being 5

anyways I can tell

pants

to ignore those files ?

Hey! A colleague of mine has been having a miserable time trying to use Pants in the one production repository we switched to Pants so far. She can’t get Pants to work at all, since it fails to bootstrap itself. This is for Pants 2.8.0 on a MacOS x86 laptop running 10.14.6. I tried to diagnose the issue with her and we kept on running into the exact same problem, independent of whether the available Python was provided by pyenv or homebrew and after diligently nuking both

~/.pex

and

~/.cache/pants

. A typical error trace is attached and any help would be much appreciated. This is a blocker for her picking up issues that touch on the repository (which coincidentally contains a new tool to validate package requirements across all our repositories that is about to go CI for all). Also, to exclude any peculiarities due to our local Python package mirror or some such, I nuked the Pex and Pants caches on my work laptop and tried to bootstrap from scratch. The results are mixed: The good news is that I was able to bootstrap and Pants does run mypy, tests, etc. The bad news is that I cannot format or lint the code anymore since Pants just can’t find the lockfile for Black. I tried regenerating the main lockfiles etc to no avail. Part of me is ecstatic about never having to deal with Pylint again, but I fear that CI nor the CTO won’t let me get away with that. Again, any help would be much appreciated.

14:24:15.68 [ERROR] 1 Exception encountered:

  FileNotFoundError: [Errno 2] No such file or directory: '/Users/grr/.cache/pants/setup/bootstrap-Darwin-x86_64/pants.DZStIS/install/lib/python3.9/site-packages/pants/backend/python/lint/black/lockfile.txt'

is pants tailor supposed to generate BUILD files in the vendor directory for go projects?

looks like there’s no codegen for protobuf + go, can you all point me in the right direction? might contribute a plugin for this. seems simple enough, especially since you already have a protobuf + python implementation

Podcast listeners, please nominate (here) some good JVM, Go, or polyglot podcasts that you think we should try to get Pants featured on. Thank you!

not sure if this is possible, but is there a pants command that’s essentially equivalent to

poetry install

? I ask because it’s convenient to be able to create a local environment for debugging that contains every package, but unfortunately i’m not able to use

poetry install

in our monorepo because of a tensorflow dependency that doesn’t work on M1 macs. [long story short: https://pantsbuild.slack.com/archives/C046T6T9U/p1642537615072100 we’re using an older tensorflow version in

pyproject.toml

(which doesn’t work on M1) and then using markers to tell pants to ignore it on M1 and install

tensorflow-macos==2.7.0

instead by setting it in a

python_requirement_library

in a BUILD file] it would be helpful if there were some pants command to create an environment with contains everything, including these additional pants constraints

there is still time to vote in 2022 roadmapping! if you haven’t yet, please take a few minutes: https://pantsbuild.slack.com/archives/C18RRR4JK/p1642626085023200

What's the proper way to handle items in

requirements.txt

that come from a repository? It seems the

python_requirement

target happily consumes these, but I got an error when pants was resolving my

constraints.txt

generated by

pip-compile

.

We're trying to run pants on M1 mac (using rosetta terminal) but its always failing with following stacktrace. Would really appreciate if someone can help out on this. Is there something which we're doing wrong? Let me know if there's already a thread somewhere related to it which I can refer to.

#9 597.1 Failed to begin watching the filesystem: Bad file descriptor (os error 9)
#9 597.1 Traceback (most recent call last):
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/bin/pants_loader.py", line 95, in run_default_entrypoint
#9 597.1     exit_code = runner.run(start_time)
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/bin/pants_runner.py", line 97, in run
#9 597.1     runner = LocalPantsRunner.create(
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/bin/local_pants_runner.py", line 119, in create
#9 597.1     options_initializer = options_initializer or OptionsInitializer(options_bootstrapper)
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/init/options_initializer.py", line 101, in __init__
#9 597.1     self._bootstrap_scheduler = create_bootstrap_scheduler(options_bootstrapper, executor)
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/init/options_initializer.py", line 74, in create_bootstrap_scheduler
#9 597.1     EngineInitializer.setup_graph(
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/init/engine_initializer.py", line 181, in setup_graph
#9 597.1     return EngineInitializer.setup_graph_extended(
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/init/engine_initializer.py", line 285, in setup_graph_extended
#9 597.1     scheduler = Scheduler(
#9 597.1   File "/home/ripplinguser/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/engine/internals/scheduler.py", line 209, in __init__
#9 597.1     self._py_scheduler = native_engine.scheduler_create(
#9 597.1 ValueError: Failed to begin watching the filesystem: Bad file descriptor (os error 9)