hundreds-carpet-28072
06/05/2025, 12:38 PMpants generate-lockfiles
goal in recent versions? I’m a few versions behind so if I can improve our generation time with a bump that would be great, before I attempt to finish my uv-based lockfile converter.dazzling-pizza-75442
06/05/2025, 1:02 PMfast-nail-55400
06/05/2025, 1:17 PMhundreds-carpet-28072
06/05/2025, 2:02 PMcurved-manchester-66006
06/05/2025, 2:42 PMdazzling-pizza-75442
06/05/2025, 2:46 PMdazzling-pizza-75442
06/05/2025, 2:48 PMwide-midnight-78598
06/05/2025, 3:04 PMthe biggest speed up we gained with resolvers was pinning as many versions as possibleThis is true across a lot of dimensions.
interpreter_constraints
and then the pip installed library versions themselveshundreds-carpet-28072
06/05/2025, 3:24 PMthe biggest speed up we gained with resolvers was pinning as many versions as possible. The biggest culprit in our case was boto. Pex/pip were checking hundreds of versions during resolution because we had a ‘>=’ version constraint in requirementsIs there a nice way of outputting this info to see if there’s any glaring bottlenecks? Previously we were using
uv
to compile a constraints.txt which is almost instant, with the Pex lockfile generation we’re looking at ~ 12-15 minutes for all requirements.fast-nail-55400
06/05/2025, 3:31 PMfast-nail-55400
06/05/2025, 3:31 PMfast-nail-55400
06/05/2025, 3:31 PM--keep-sandboxes=always
for the generate-lockfiles
goal and then running the sandbox for the lockfile generation manually would let you do so.wide-midnight-78598
06/05/2025, 4:22 PM