https://twitter.com/pypi/status/1449021102416662547 Pants Build retweeted: We want to hear from companies and community projects using PyPI as a team! If your team wants to contribute to he… https://twitter.com/i/web/status/1449021102416662547 Twitter

https://twitter.com/pantsbuild/status/1449107317253939200 All of your favorite Python tooling under a consistent UX, highly extensible, OSS, smart caching that lets you move fast, and without nearly as much boilerplate as you're used to with competing systems. Learn more at https://t.co/TGAn4kfBVl. Come chat at https://t.co/1BfDfT7fnc. Twitter

Like Pants? Here are some ways you can help more people benefit: • Tell peers why you use Pants and who you think will benefit from Pants too. Spread the word! Whether that be in a casual chat, tweet, blog post, tutorial, presentation, or video. • Contribute to the collaborative spirit of the community by helping a fellow user on Slack or GitHub. • Contribute to the docs using the "Suggest Edits" button. • Contribute to the codebase by suggesting an idea, making a feature request, giving feedback on an issue or dev release, opening an issue, or starting a pull request. • List your organization or open source project on the Who Uses Pants page https://www.pantsbuild.org/page/who-uses-pants • Add a testimonial https://www.pantsbuild.org/docs/testimonials • Publish a case study of how your goals are being served by Pants. This is easily one of the most powerful things you can do! • Ask your organization to consider partnering with us on things like adding support for JavaScript https://www.pantsbuild.org/page/language-support, other languages, or a key new feature. The more resources, the faster we can add that one more thing you've been eagerly waiting for...

Another bike shed 🎨 We're adding a new goal to automate upgrading Pants versions by updating BUILD files to fix deprecations for you. Trying to come up with the name, currently between

./pants mend

vs

./pants serge

. Feedback welcomed! 🧵

Hi all!

I'm inhering a python project with pants 1.30.1. And I'm a Node.js developer... So, long story short. I want to add a new python module, I've added it in the requirements.txt, but now I don't know how to make pants "add" that module. When does that happen?

hey folks, just FYI: one of my teams is prepping a series of blog posts around Notebooks at Twitter and I think we'll finally have a chance to plug https://github.com/pantsbuild/pants-jupyter-plugin in the opening post to a pretty wide audience - happy to share a preview of that when its finalized. we're shooting for EOQ but it may come sooner (we're in second rev draft editing now).

Getting this message from time-to-time when running commands, even though my interpreter_search_paths is set to

/usr/bin/python3

which is definitely there... Anybody know what this means?

08:28:54.05 [WARN] Completed: Find Python interpreter to bootstrap PEX - No bootstrap Python executable could be found from the option `interpreter_search_paths` in the `[python-setup]` scope. Will attempt to run PEXes directly.

A poll: should the new

./pants update-build-files

use Black by default, or you have to opt into it with an option? Beyond autoformatting, the goal automates fixing some safe deprecations like renaming target names + for opt-out, - for opt-in. Comments also welcomed :)

hey team. An interesting behaviour worth sharing — a MacOS user runs

./pants run project/script.py

. The user has a Python 3.7 interpreter accessible on the

PATH

which Pants finds but reports it needs Python 3.8 to run this particular script in the monorepo. User makes an installation of Python 3.8 version (which replaces the Python 3.7 on

/usr/bin/python3

) and re-runs

./pants run project/script.py

. Pants can’t still find the new interpreter. Note that user has been successfully able to work with the Pants monorepo when running targets that required Python 3.7 version. What has helped:

$ rm -rf .pids && rm -rf .pants.d

in the local monorepo directory and restart computer, but the issue persists.

$ rm -rf /Users/user.name/.cache/pants

and restart. Pants is now able to find the new Python interpreter. Could it be that Pants caches the

/usr/bin/python3

version so that any subsequent changes to that shim won’t have any effect unless the

/Users/user.name/.cache/pants

is removed?

https://twitter.com/PyDataBristol/status/1450061682269736961 Pants Build retweeted: Have you tried PyPy yet? Give it a go! It’s FAST. 🔥 On average it benchmarks 5x faster than CPython. It won’t do… https://twitter.com/i/web/status/1450061682269736961 Twitter PyPy 7.3.6 triple release! Support for cpython versions 2.7, 3.7 and for the first time a beta release of 3.8 suppo… https://twitter.com/i/web/status/1449779817042305025 Twitter

Hey Pants Team, seeing a new error when bootstraping pants:

Error: 6.38 [ERROR] 1 Exception encountered:

Engine traceback:
  in select
  in pants.init.plugin_resolver.resolve_plugins
  in pants.backend.python.util_rules.pex.create_venv_pex (pants_plugins.pex)
  in pants.backend.python.util_rules.pex.build_pex (pants_plugins.pex)
  in pants.backend.python.util_rules.pex.build_pex_component (pants_plugins.pex)
  in pants.backend.python.util_rules.pex_cli.setup_pex_cli_process
  in pants.backend.python.util_rules.pex_cli.download_pex_pex
  in pants.core.util_rules.external_tool.download_external_tool
  in downloaded_file
Traceback (no traceback):
  <pants native internals>
Exception: Client error (403) downloading file pex from <https://github.com/pantsbuild/pex/releases/download/v2.1.44/pex>
Traceback (most recent call last):
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/bin/daemon_pants_runner.py", line 124, in single_daemonized_run
    scheduler, options_initializer = self._core.prepare(options_bootstrapper, complete_env)
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/pantsd/pants_daemon_core.py", line 129, in prepare
    build_config, options = self._options_initializer.build_config_and_options(
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/init/options_initializer.py", line 107, in build_config_and_options
    build_config = _initialize_build_configuration(
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/init/options_initializer.py", line 47, in _initialize_build_configuration
    working_set = plugin_resolver.resolve(options_bootstrapper, env)
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/init/plugin_resolver.py", line 123, in resolve
    for resolved_plugin_location in self._resolve_plugins(options_bootstrapper, env):
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/init/plugin_resolver.py", line 146, in _resolve_plugins
    session.product_request(ResolvedPluginDistributions, [self._request])[0],
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 562, in product_request
    self._raise_on_error([t for _, t in throws])
  File "/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.7.0_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 497, in _raise_on_error
    raise ExecutionError(
pants.engine.internals.scheduler.ExecutionError: 1 Exception encountered:

Engine traceback:
  in select
  in pants.init.plugin_resolver.resolve_plugins
  in pants.backend.python.util_rules.pex.create_venv_pex (pants_plugins.pex)
  in pants.backend.python.util_rules.pex.build_pex (pants_plugins.pex)
  in pants.backend.python.util_rules.pex.build_pex_component (pants_plugins.pex)
  in pants.backend.python.util_rules.pex_cli.setup_pex_cli_process
  in pants.backend.python.util_rules.pex_cli.download_pex_pex
  in pants.core.util_rules.external_tool.download_external_tool
  in downloaded_file
Traceback (no traceback):
  <pants native internals>
Exception: Client error (403) downloading file pex from <https://github.com/pantsbuild/pex/releases/download/v2.1.44/pex>

(Use --no-process-execution-local-cleanup to inspect chroots and/or -ldebug for more logs. See <https://www.pantsbuild.org/v2.7/docs/troubleshooting> for common issues. Consider reaching out for help: <https://www.pantsbuild.org/v2.7/docs/getting-help.>)
Error: Process completed with exit code 1.

any way we can prevent this?

Hi team, looking for some help . My team's CI is failing as pants is getting a 403 downloading coursier( it happened while running

pants test

) . Is this a known issue ? Also potentially related. I tried to reproduce the issue in on my local environment . I deleted the cache and tried to boostrap pants from scratch ( similarly to our CI) and that is failing too. We are using pants 1.35rc1 and can provide the toml if needed. UPDATE : Issue seems transient. Our CI is back on track and my local environment was able to bootstrap itself again without issues.

https://twitter.com/di_codes/status/1450170487418626049 Pants Build retweeted: This survey is hugely important for helping @ThePSF understand our users, how things are changing, and prioritize w… https://twitter.com/i/web/status/1450170487418626049 Twitter We are happy to announce the Python Developers Survey 2021! Take part in the official Python Developers Survey 202… https://twitter.com/i/web/status/1450168556801380357 Twitter

https://twitter.com/semaphoreci/status/1450417454983876609 Pants Build retweeted: Choosing a repository strategy is not only a technical matter but also about how people communicate. Multirepos all… https://twitter.com/i/web/status/1450417454983876609 Twitter

Why does pants complain about symlinks which are absolute links? We have a few places in our development environment where we symlink files with absolute paths. The source and target are both within the repository, but the target path is absolute. These files give us an error–

Exception: Failed to read link "/Users/ryan.king/code/color/.git/hooks/post-checkout": Absolute symlink: "/Users/ryan.king/code/color/.git/hooks/post-checkout"

Now that we have the goal

update-build-files

, would you find it helpful to have automated support for renaming targets and updating all their references? Something like this maybe:

[update-build-files]
rename_targets = { path/to:original_name = path/to:new_name }

Pants will update all references to the target, e.g. in the

dependencies

field. How often do you find yourself renaming targets? (Utility probably depends on how much you use dependency inference)

Hi everyone, Happy to join you guys 😉

hello! In pants 2.7.0 I’m running pants tailor and it.. is adding pex_binary targets to my build files? Is there some way to turn this off

Another "feel like I'm missing something obvious"--can you specify a local wheel file as a third-party requirement somehow? Got some third-party library prototypes I'm trying to use and I don't want to pantsify them, but I can build local wheel files, but I don't want to set up a private index just for these...

https://twitter.com/pycascades/status/1450507869237903363 Pants Build retweeted: 🐍 FINAL WEEK 🐍 The PyCascades 2022 call for proposals closes this Sunday, Oct 24th! Now is the time to submit th… https://twitter.com/i/web/status/1450507869237903363 Twitter

https://twitter.com/PythonWeekly/status/1450854368530636800 Pants Build retweeted: Streamline your Docker builds with Pants via @pantsbuild https://buff.ly/3aSI2u1 #Python #Docker #Pants Twitter

Hmm... I have a library that has BUILDs in all its submodules for fine-grained dependency resolution. But for one pex, I need the whole thing packed in because the pex will be used to evaluate other files (so the fine-grained dependency won't work as the other files may need one of the libraries). But adding just the top-level dependency didn't work (it of course just brought in the stuff from the top-level BUILD). I can add all the subtree targets manually, but is there nomenclature for bringing in "every dependency under this one" for that sort of use case? (sorry, I feel like I've asked this before). I could of course just make the top BUILD have sources like

**/*.py

but that loses the point of the fine-grained resolution when I need it.

(I've done the above since that was a small lib, but this will come up again fairly soon with a bigger lib)

I tried "//this/library::" but the "::" didn't work (fair, really, but thought I'd try)

Is there a way for pants to read in a

.env

file as environment variables when running an integration test? Or do I need to add it as a file target and load via python-dotenv?

https://twitter.com/Yhg1s/status/1450908937633636352 Pants Build retweeted: The Python Steering Council posted our current thoughts on type annotations (specifically PEP 563/649, and 'from __… https://twitter.com/i/web/status/1450908937633636352 Twitter

https://twitter.com/ThePSF/status/1450869469950140420 Pants Build retweeted: Know someone who should be a PSF Fellow but isn't yet? Nominate them before November 20, 2021, and we will add them… https://twitter.com/i/web/status/1450869469950140420 Twitter

I'm doing some Python development for ARM. I don't have an ARM device but our CI produces an arm64 .pex file. Sometimes I then go to test it on a device and discover I've got like a one line typo I'd like to quickly fix and test. Does anyone know of an easy way to unzip a .pex, edit it, and then re-zip it? I did come up with the following to run an un-zipped pex:

PYTHONPATH=$(echo $(pwd)/.deps/* | tr ' ' ':') python -m device.session.main

but that's a bit ugly and I don't know how to convert that back to a

.pex

easily (I think I could figure out some flags to tell it to use the

.deps

, not to check

pypi

, etc. but is there an easier way?

Are there any vs code users here? What is there support for syntax highlighting for BUILD files?