is it possible to specify a commit hash for a lint...
# general
h
is it possible to specify a commit hash for a linter version? i tried this in
pants.toml
but it didn’t work
Copy code
[pylint]
config = ".pylintrc"
version = "<git+git://github.com/PyCQA/pylint.git@e75e37a2908ef1c003ea5816c1e234523bdd38be#egg=pylint>"
lockfile = "pylint.lock"
as in, it fails when i try generate the lockfile
Copy code
./pants generate-lockfiles --resolve=pylint
h
Yeah unfortunately VCS requirements do not work with tool lockfiles as a limitation of Poetry: https://github.com/pantsbuild/pants/issues/13965 That ticket and https://github.com/pantsbuild/pex/issues/1556 ponder how we should handle VCS requirements when we switch to Pex for lockfile generation..feedback very welcomed, as it's not clear how to lock down a VCS requirement, such as if you use a branch rather than commit SHA.
So for now, you'd either need to a) give up on using a lockfile. You can mostly recreate it by putting all the transitive dependencies in
[pylint].extra_requirements
. b) Build your VCS requirement as a wheel and host it somewhere, then pull that
💯 1
h
Thanks Eric, I thought it was some syntax error on my part, but it sounds like it’s just currently not possible to use a lockfile in those cases.
👍 1