👖 2.21 pre-release testing! The next major release 2.21 is starting to stabilise. It'll help you and help us if you can test it out: your upgrade will be smoothest if we can find any regressions/bugs/issues before releasing! 1. Edit

pants.toml

to say

pants_version = "2.21.0a1"

2. Run your favourite commands, like

pants lint ::

3. Run it in your CI, if possible 4. If you have time, take a look at the new features and try out any that are relevant to you! 5. If you find some issues or have some questions, please ask here or file an issue! This release has got a bunch of good stuff, here's some highlights: • All built-in backends now support the

[test].attempts_default

option to automatically retry tests. • Significant speed-ups when manipulating Python dependencies, especially huge ones like PyTorch. • When a

pants test ...

run in CI fails, the summary now includes suggested invocation to copy-paste and re-run locally. • The

__defaults__

symbol now applies to targets generated by a target generator, in addition to targets written literally in BUILD files.

Nice! I literally came here to ask about speed with pytorch. 😬 Happy to see this one!

Significant speed-ups when manipulating Python dependencies, especially huge ones like PyTorch.

@broad-processor-92400 The "Significant speed-ups when manipulating Python dependencies" - that applies to built-in fix/fmt/lint tools as well right? I upgraded one of my projects, and it "felt" snappier, and after some cache wiping and timing of

pants fix fmt lint ::

- there's about 1.5 to 2 seconds of speed-up (11ish to 13ish seconds) on already passing files. I haven't deep dived, but it looked like it came from creating the tool pexes (since the runtime of the tools themselves is pretty solid)

yeah (and the tables in https://github.com/pantsbuild/pants/pull/20670 are rendered better), and here's what I see on my biggest repo at work: