By the way, the V2 implementation of

./pants binary

and

./pants run

is ready to use 🙂 To try it out, run

./pants --no-v1 --backend-packages2='pants.backend.python' binary path/to:python_binary_target

(FYI, the

--no-v1

means don’t use the V1 implementation of

binary

too. If you had

--v1 --v2 binary

, then you would create it both with V1 and V2, which you probably don’t want because it’s a waste of time to create the same binary twice.)

is this ready to be used from version 1.25.0

Yes, the one current limitation is that we ignore some fields like

zip_safe

in your BUILD file. I’m working on fixing that as we speak and the next weekly dev release should have full feature parity to V1. Some of the upsides for using V2 binary are: * smarter caching * less verbose output * avoids irrelevant work that V1 does - should be faster * works more ergonomically with custom target types