https://pantsbuild.org/ logo
Join Slack
Powered by
I know not using lockfiles is deprecated, but it's...
# general
a
I know not using lockfiles is deprecated, but it's a big pain for some people... Currently, if you want to opt out, you have to go through a whole song and dance whenever you need to update the lockfiles for tools (change your pants.toml, regenerate them, change it back, commit). Is there any reason for this, or it's just something that nobody brought up?
If nothing else, this could be made trivial by the ability to unset settings on the command-line/via env vars. I couldn't find documentation, or how to do it, but if you could unset 
python.requirement_constraints
, you could do it like that, and it wouldn't be such a pain
c
Most settings have companion cli flags/env vars. ex: https://www.pantsbuild.org/dev/reference/subsystems/python Is that the sort of thing you were looking for?
a
Yes, but as far as I can tell, there's no way to REMOVE a setting that's set in the config file.
c
No way to pass 
None
on the cli?
a
None that works, that I could find out.
Basically, to regenerate lockfiles for tools, which you have to use now, I go and toggle the comment on these 2 lines now. I can set 
python.enable_resolves
to 
True
, but cannot unset 
python.requirement_constraints
, so regenerating lockfiles sucks.
The sad part, we also have a default for that, so we still do the same thing, it's just one extra step
And, no, we can't use lockfiles for everything, I finally gave up, on a PR with like 60 commits and 200k+ added lines
image.png
6 Views
Open in Slack
PreviousNext
Powered by