Is v1.26 or v1.27 the next release? What distinguishes these two releases?

Hello! There are a couple releases in process: * 1.26.0rc2 * 1.27.0rc0 * 1.28.0.dev0 The reason there are so many is that we always have a weekly release, but after about 3-5 releases we branch off a stable release series, like 1.26.x. We use as many release candidates as necessary for a final “stable” release like 1.26.0 to be released. When testing RCs (release candidates), we try to fix any bugs, including performance bugs, found by users in testing out the series. 1.26.0 has taken a particularly long time to land because it upgrades from Pex 1.0 to Pex 2.0, which was a major rewrite of Pex to use Pip to resolve dependencies instead of its own custom resolver. This generally works much better, but there’s one remaining issue with increased network usage. -- If you want the latest and greatest, we recommend 1.28.0.dev0 (it’s what we use at Toolchain). In particular, if you’re using the V2 implementation of Python documented at https://pants.readme.io/docs, we recommend 1.27.0rc0 or 1.28.0.dev0 because it makes several improvements to that experience. You can see release notes at https://www.pantsbuild.org/notes-master.html.

Thank you for laying it out. I saw there was a network issue. pantsbuild is waiting for

pip

to implement a change for that one, if I was following the slack stream correctly.

Cool. You’ll want to stay on 1.25.x, then, for now. The post right below this is about a fix to the network request issue

I am interested in the V2 improvements so I will test out

1.27.0rc0

.

Awesome! Please let us know if we can help with anything or you find any issues. See https://github.com/pantsbuild/example-python for an example Python repository demoing how to turn on V2 and how to use all its features (Warning that the very first time you run something like

./pants test

will be slower than we’d like because we have to download all your 3rd party dependencies. We’re working to speed this up. After the first run, the cache will kick in and it should be much faster.)

erk?!

example-python/helloworld/main.py

but but where is all the

pants

bureaucracy directories? 🧌 Now I'm going to have to update our documentation and not indoctrinate every new hire into why

helloworld/src/python/helloworld

makes sense. I see

1:1:1

is still a thing. 👍 I have some RTNewM to do.

Hehe you can still use

src/python

if you want 😉 it’s particularly useful for polyglot repos (i.e. multiple languages). But, if you just have Python, then indeed it is much simpler to drop the

src/python