Andreas Stenius
Andreas Stenius
@jsirois FYI, for brew, we have this line in order to make it executable at all (as it wouldn't show a dialog where you could select to go ahead any...
I agree with @sureshjoshi about this being mostly of the bandaid kind. The better approach I think would be to not rely on CWD as much as we do now...
Deprecate using Python 3.7 with default tool lockfiles, preparing for pip 24.1 / Python 3.13 support
If we provide two lockfiles per tool, switching between them would be easier, and we could issue warnings when using the old one, which could be the default initially.
It would be nice if it was less involved to override which version of black to use. i.e. provide the version and pants takes care of the locking and what-not...
Clearly, I need to dig deeper, as I've tried this fix out, and it didn't seem to help: ``` The conflict is caused by: acme-pants-plugin 2.21.0.dev11+2.21.0 depends on pantsbuild-pants==2.21.0 The...
This is a net-zero change, only makes the distribution name in the `Requires-Dist:` line use `pantsbuild-pants` instead of `pantsbuild.pants`, which is the normalized form used by `packaging` (PyPA).
> It's not obvious to me why this is an improvement. Why normalize the name like this? It gets normalized where it matters in rules, right? I think this matters...
Is this a bug, though? feels more feature to me.. :)
I guess you meant: ```python terraform_module(dependencies=[":lock"]) file(name="lock",source=".terraform.lock.hcl") ```
Using synthetic targets could work, as long as they don't need data about other targets when being generated. i.e. if enumerating modules is about files on disk, rather than discovering...