Closed sjincho closed 2 weeks ago
Similar issue: https://github.com/pex-tool/pex/issues/2389
Thanks for the report and repro. I will note, like #2389 this is a definitely bug, but also a weird use of a lock file. Since a lock is locked already, passing something like --only-binary ansicolors
when using the lock doesn't make much sense. It would make a bit more sense if Pants didn't pass all these extra args when using a lock (as opposed to creating or updating one).
The fix for this is now released in Pex 2.4.1: https://github.com/pex-tool/pex/releases/tag/v2.4.1
I'm using pex 2.3.1 on Ubuntu 22.04.
If I create a lock file using:
and run
it works w/o problem.
But running:
yields the following error:
In Pants 2.21.0, it seems like a change that uses pex to handle binary wheels was introduced. https://github.com/pantsbuild/pants/pull/20598
Due to this change, pants always passes both
--lock
and--only-binary
flags, causing https://github.com/pantsbuild/pants/issues/21077