I upgraded pants to 2.16 (from 2.14) and I am noti...
# generall
little-train-28371
08/02/2023, 11:00 PMI upgraded pants to 2.16 (from 2.14) and I am noticing an increase in packaging time and even not able to complete at all (i interrupt the build after 5 min). The package targets are cloud functions.
On pants 2.14, package finishes in under a minute. Anyone experiencing similar issue?
little-train-28371
08/03/2023, 3:24 AMThis turned out to be an issue with the default pip not resolving .. ever.
little-train-28371
08/03/2023, 3:25 AMsetting it to a newer pip version fixed the issue
Copy code
[python]
pip = "23.0.1"little-train-28371
08/03/2023, 3:27 AMthere is though an increase package build from ˜46 secs to ˜77 sec
b
broad-processor-92400
08/03/2023, 5:07 AMDo you use “resolves” and lock files for your Python code?
broad-processor-92400
08/03/2023, 7:34 AM(To spell that out a bit more, now that I'm on a computer)
Enabling "resolves" allows generating lockfiles, which mean the dependency resolution process only needs to run once and is saved in the repo. This has two major benefits:
• faster builds, because the lockfile saves the appropriate dependency versions, without needing to go and rerun resolution/check PyPI
• reproducible/stable builds, if new dependency versions are published, builds will still reference the original versions, so there's less risk of a build breaking randomly.
https://www.pantsbuild.org/docs/python-lockfiles has more info
l
little-train-28371
08/03/2023, 9:56 PMwe don’t use locks (no particular reason). I will it give a try. I guess it won’t help with c/rust extensions, like cryptography/cffi in the sense that the ci image where the applications are packaged needs to have a compatible environment to where they are going to be running.
2 Views