Is it possible to avoid building pex every time I ...
# generals
square-psychiatrist-19087
06/26/2025, 9:55 PMIs it possible to avoid building pex every time I want to run a tool?
square-psychiatrist-19087
06/26/2025, 9:56 PME.g. running
pants --only=mypy ::h
happy-kitchen-89482
06/26/2025, 10:17 PMbuilding the pex fails? Or running it?
s
square-psychiatrist-19087
06/26/2025, 10:20 PMBuilding
h
happy-kitchen-89482
06/26/2025, 10:23 PMIf the third-party deps need to be present when the tool is run then I don’t see how this is avoidable
s
square-psychiatrist-19087
06/27/2025, 6:47 AMI was thinking to use uv instead of pex, creating symlinks is much faster than putting it all into pex, but that would require rewriting mypy backend, am I right?
h
happy-kitchen-89482
06/28/2025, 3:26 AMIt would require rewriting a huge chunk of the Python backend…
happy-kitchen-89482
06/28/2025, 3:26 AMAnd uv does not yet have all the features we would need, anyway
happy-kitchen-89482
06/28/2025, 3:27 AMBut the pex we create should not be a zipfile, it should be, basically, a symlink farm venv
happy-kitchen-89482
06/28/2025, 3:27 AMAlthough maybe that depends on a setting, I don’t quite remember
happy-kitchen-89482
06/28/2025, 3:28 AMI’m assuming you have a lockfile?
s
square-psychiatrist-19087
06/28/2025, 6:48 AMI have a lockfile for mypy resolve and a lockfile for other code with a lot of 3rdparty dependencies.
Anyway, I'll be debugging what exactly eats 50gb memory in CI, maybe it accumulates in some different place
square-psychiatrist-19087
06/28/2025, 6:49 AMThank you
7 Views