Are the generated lockfiles (3rdparty/python/default.lock) meant to be under version control in the same way that poetry lockfiles are, and manually regenerated when stated requirements change? (sorry, trying to understand the, er, dependencies of dependency lists. We were using a constraints.txt style "lockfile" which was a pip freeze of a venv with everything installed (including transitive 3rd-party dependencies we don't directly mention anywhere). Looks like Pants can now generate that full lockfile (and we could only generate

python_requirements

for our direct dependencies) but I wasn't sure of that yet)