<#18624 `pants generate-lockfiles --resolve=foo` w...
# github-notifications
c
#18624 `pants generate-lockfiles --resolve=foo` w/o a `python_requirements` targets does the wrong thing Issue created by kaos Describe the bug I was surprised to learn that I could run
pants generate-lockfiles --resolve=pytest
after setting up the requirements file and configured the resolve in
pants.toml
but not having any
python_requirements
targets yet. Pants version 2.16.0a1 OS Mac Additional info The result is an empty lockfile, completely disregarding the contents of my
pytest.txt
requirements file. For tools, it feels kind of weird that it is required to have a
python_requirements
target in order for it to work. Regardless, I think it should fail rather than happily produce an empty lockfile in this case. pantsbuild/pants