fyi new upgrade tip in docs: check if the

./pants

script has any updates. https://www.pantsbuild.org/docs/upgrade-tips#check-for-updates-to-the-pants-script thanks @rapid-bird-79300 for the suggestion!

Hello, excellent Pants team. I'm failing to bootstrap-install pants on this Ubuntu machine. I run

./pants --version

and it warns

Failed to create the file virtualenv.pyz: Permission denied

and later fails

FileNotFoundError: [Errno 2] No such file or directory: 'virtualenv.pyz'

SHA256 of <https://raw.githubusercontent.com/pypa/get-virtualenv/20.4.7/public/virtualenv.pyz> is not as expected. Aborting.

I ran ./pants as plain ol' me, I didn't sudo or anything. But I'm happy to try again with sudo if that will help; or to tweak the permissions on some dir or other; or whatever.

Poking around in

pantsbuild/setup

, I thought to try mktemp'ing a directory, cd'ing into it, and curling that file, thinking maybe I could recreate the problem. But curl created the file just fine. Hmm.

Having added some printf-like debugging to

./pants

, I see I should be trying to curl that file while in

~/.cache/pants/setup/bootstrap-Linux-x86_64/pants.ZiYnGN

. and there the curl indeed fails with Permission denied. I did some naive looking at permissions, but didn't notice anything.

Edited my pants to use

wget

instead of

curl -LO

.

pants --version

finishes, huzzah!

Hey Larry! What's your umask? I can repro a permission denied touching a file in a mktemp -d dir when umask is 0666 for example, but you'd have more general issues I'd think with that umask. Is this a bare-metal machine or a docker container?

That umask is 0002. This is a bare-metal machine. Focusing on the weird fact: when I used a mktemp-created dir under some arbitrary dir, curl succeeded; but curls in setup's dir under ~/.cache failed: I tried cd-ing up the directory tree and doing a curl each time. It failed in ~/.cache and in its subdirs; succeeded above in my homedir.

Further experimentation suggests: Hidden-ness matters?! In my homedir, I mktemp -d blork.XXX , cd into it, curl , success. Then in my homedir, mktemp -d .blork.XXX , cd into it, curl fails. lolwut

I guess I'm hitting a bug in a new curl. (I installed curl so I could install pants; I normally use wget). Curl version on fails is

7.76.1

. If I snap remove curl, apt install curl, I get an older version

7.68.0

. That older version works. ...and when I get the latest curl version

7.77

from the curl site, it works. So I guess I just had unlucky timing when I got curl. Sorry for the noise, folks.

https://www.pantsbuild.org/docs/python-linters-and-formatters#skipping-a-formatter-or-linter I think this is now wrong.

InvalidFieldException: Unrecognized field `skip_black=True` in target test/python/sportr_utils:tests. Valid fields for the target type `python_tests`: ['dependencies', 'description', 'interpreter_constraints', 'runtime_package_dependencies', 'sources', 'tags', 'timeout'].

Edit: New in 2.5.0 !

attempting to upgrade our pants script and we get this error in CI:

./pants version

Bootstrapping Pants using /usr/bin/python3.8

Downloading the virtualenv zipapp

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed


  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 20 9258k   20 1879k    0     0  5910k      0  0:00:01 --:--:--  0:00:01 5891k
100 9258k  100 9258k    0     0  17.5M      0 --:--:-- --:--:-- --:--:-- 17.5M

SHA256 fingerprint of <https://raw.githubusercontent.com/pypa/get-virtualenv/20.4.7/public/virtualenv.pyz> verified.

Installing pantsbuild.pants==2.5.0 into a virtual environment at /home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/2.5.0_py38

Traceback (most recent call last):

  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main

    return _run_code(code, main_globals, None,

  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code

    exec(code, run_globals)

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/__main__.py", line 168, in <module>

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/__main__.py", line 164, in run

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/__main__.py", line 18, in run

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/__init__.py", line 30, in cli_run

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/__init__.py", line 48, in session_via_cli

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/__init__.py", line 75, in build_parser

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/plugin/seeders.py", line 8, in __init__

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/plugin/base.py", line 39, in options

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/plugin/base.py", line 18, in entry_points_for

  File "/home/ubuntu/workspace/PR-58095/./.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-20.4.7/virtualenv.pyz/virtualenv/run/plugin/base.py", line 18, in <genexpr>

  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load

    module = import_module(match.group('module'))

  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module

    return _bootstrap._gcd_import(name[level:], package, level)

  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import

  File "<frozen importlib._bootstrap>", line 991, in _find_and_load

  File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked

  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed

  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import

  File "<frozen importlib._bootstrap>", line 991, in _find_and_load

  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked

ModuleNotFoundError: No module named 'virtualenv.seed.via_app_data'

We run Ubuntu 20.04 in CI with Python 3.8. This does not happen with our local runs. Any idea how to resolve this error?

https://twitter.com/pantsbuild/status/1407061291882135553 A build system brings order, speed, and quality-checking to your builds. In this quick 2:27 minute video, learn more about what build systems are and how Pants Build orchestrates your favorite Python tools to make them even better. https://t.co/wTjO4ANh6z Twitter

https://twitter.com/pantsbuild/status/1407102642933796875 New blog post! "Pants is now published for Apple Silicon (M1) or: How to avoid making perfect the enemy of the good". https://t.co/ExAI9gCNEg Twitter

https://twitter.com/EArellanoAZ/status/1407104279513468935 Pants Build retweeted: Some of my thoughts on open source: "successful open source projects are full of trade offs between purity vs. prag… https://twitter.com/i/web/status/1407104279513468935 Twitter New blog post! "Pants is now published for Apple Silicon (M1) or: How to avoid making perfect the enemy of the good… https://twitter.com/i/web/status/1407102642933796875 Twitter

so, managed to fold a few libraries that we publish to a local pypi repository into a pants repo. written a plugin to generate a version number when you run

pants package

What's the recommended way of shipping these to the repository? More pants extensions?

I am trying to run some pytests with pants 2.0.2. These specific tests run a subprocess command in a function that interacts with

git

. I am getting the following error:

fatal: not a git repository (or any of the parent directories): .git

I have found that this is because with pants 2 the root where the tests run is

/private/var/folders/89/r169_6497n15qnqm0bfhnjlr0000gp/T/process-executionzY6hQB

which does not include my “.git” config files. With pants v1 all of these tests ran without issue and im assuming the root was the “build root”. I have tried adding a global

resource

that includes the

git

files necessary but that is not working. Is this as simple as changing the

rootdir

of the global pants options? I would like to not have things running “inside” of my build root as it could cause other issues. Any other suggestions?

I could have sworn I saw somewhere in the docs there's a way to use a

python_distribution

instead of a

python_library

in tests. ... I have a library that I'm trying to bring into the fold that makes heavy use of setuptools entrypoints and ... stuff. Which doesn't seem to play nice at all with pants.

https://twitter.com/pantsbuild/status/1408083336975765513 See you today+Fri @buildmeetup! Pants Build maintainer @stuhood is presenting on Fri re speculation. Maintainers are available throughout the conf to chat with you about Pants, its @Rustlang engine, REAPI, build tools, Python ❤️, shell scripting ❤️, ergonomic software design, etc Twitter

Pants longtime maintainer @witty-crayon-22786 is currently available at the Pants breakout room at Build Meetup. Feel free to stop by right now with any questions you've been too shy to ask here on the Slack. https://build21.venueless.events/rooms/06ff87ea-e2c7-41d1-8fd7-05a3a655b8d5

hi, I’ve a python distribution questions. I’ve a package that I want to distribute with some of its dependencies in

extras_requires

Pants correctly adds them to

extras_requires

in the generated setup.py . How do I tell Pants to not add them in

install_requires

?

The docsite got a coat of paint today: https://www.pantsbuild.org/

https://twitter.com/pantsbuild/status/1408083336975765513 Pants Build retweeted: See you today+Fri @buildmeetup! Pants Build maintainer @stuhood is presenting on Fri re speculation. Maintainers ar… https://twitter.com/i/web/status/1408083336975765513 Twitter

https://twitter.com/sc_codeUM/status/1408059478939893761 Pants Build retweeted: One of the biggest things I pushed my last company do was adopt this view of tests, and that perspective shift reor… https://twitter.com/i/web/status/1408059478939893761 Twitter One of the most overlooked benefits of automating tests is how they serve as living documentation of how your system is supposed to behave. Twitter

https://twitter.com/gvanrossum/status/1402756021358006272 Pants Build retweeted: We're hiring for "Faster CPython"! https://careers.microsoft.com/us/en/job/1059714/Principal-Software-Engineering-Manager, https://careers.microsoft.com/us/en/job/1062976/Senior-Software-Engineer Twitter

https://twitter.com/ThePSF/status/1403000510358036482 Pants Build retweeted: Did you know that @ThePSF has hosted 18 PyCon US conferences over the past two decades? Help us continue to host fu… https://twitter.com/i/web/status/1403000510358036482 Twitter

Working on an addition for the How Does Pants Work page of the docs. How's this?

Remote caching enables your coworkers and your CI to reuse the results of commands you already ran. Pants dependency inference gives you a remote execution plan for free. The engine can delegate work to a remote build cluster so that you are no longer limited by the number of cores on your machine. If you have enough remote workers, you can run your entire test suite in total parallelism.

Hi! This is a PEX problem - is it possible to get a python process to load the venv which defined by a PEX (better to use the same procrss). Example application is Ray.io lib wheee we want the remote workers the load Venv packaged in a PEX

Hello. So I am in the process of moving our main repo over to pants 2. Our “dev” environment that is run for each developer runs as follows. • centOS ec2 instance that runs a set of docker containers • each docker container uses the same base image • Pants (along with all of thee code) is bind mounted into the containers • the entrypoint and command for each docker container is a

./pants run

command. This all worked great with pants v1 and we mounted in the cache so everything was quick and worked well. With pants 2 if i start up one container everything works just fine, when we start up more than 1 container i get the following error.

config-v1                           | 22:06:54.17 [ERROR] Exception caught: (pants.engine.internals.scheduler.ExecutionError)
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 289, in run
config-v1                           |     engine_result = self._run_v2()
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 195, in _run_v2
config-v1                           |     return self._maybe_run_v2_body(goals, poll=False)
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 217, in _maybe_run_v2_body
config-v1                           |     poll_delay=(0.1 if poll else None),
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/init/engine_initializer.py", line 127, in run_goal_rules
config-v1                           |     goal_product, params, poll=poll, poll_delay=poll_delay
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/engine/internals/scheduler.py", line 569, in run_goal_rule
config-v1                           |     self._raise_on_error([t for _, t in throws])
config-v1                           |   File "/home/centos/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.2_py36/lib/python3.6/site-packages/pants/engine/internals/scheduler.py", line 539, in _raise_on_error
config-v1                           |     wrapped_exceptions=tuple(t.exc for t in throws),
config-v1                           |
config-v1                           | Exception message: 1 Exception encountered:
config-v1                           |
config-v1                           |   Exception: Failed to begin read transaction: Resource temporarily unavailable

I suspect this has something to do with how we are mounting in the cache dirs: IE we mount

~/.cache/pants -> ~/.cache/pants

If we do not mount in the cache all the services come up no problem but each has to build and resolve all the constraints first which takes a long time. Any thoughts here? Am I missing something? Any suggestions on what to try to resolve this?

Does anybody know of a Docker plugin for Pants? I saw there was one for Pants v1 but I couldn't find one for v2...

im unaware of one… curious of what the best practice for this is… seems like its trying to share the main pants process when trying to run many pants processes inside containers. all i want to share is the cache