is it possible to specify a commit hash for a linter version

Question

is it possible to specify a commit hash for a linter version i tried this in `pants toml` but it didn t work ``` pylint config = pylintrc version = <git+git github com PyCQA pylint git e75e37a2908ef1c003ea5816c1e234523bdd38be egg=pylint> lockfile = pylint lock ```

high-energy-55500 · Answer

as in it fails when i try generate the lockfile ``` pants generate lockfiles resolve=pylint```

hundreds-father-404 · Answer

Yeah unfortunately VCS requirements do not work with tool lockfiles as a limitation of Poetry That ticket and 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

hundreds-father-404 · Answer

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

high-energy-55500 · Answer

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