Ignas Anikevicius
Ignas Anikevicius
I am inclined to just merge this as is as this improves the compatibility. Any objections @rickeylev?
Could you please rebase? I think the changelog would be weirdly formatted if we merge as is.
I am not sure if this is a doc issue where we just ask the users to create an empty file. At the end of the day this is something...
Note, that `pip_parse` is non-hermetic because it is a repository rule. I think your suggested workaround looks good. I'll close as not-planned to clear up the issue back log a...
Yes, you need a system interpreter for now (#691) and you need to use something like `uv pip compile` (with extra flags) or the built in rule that is documented...
We have had a breaking change policy that we created to avoid causing too much pain for the users when we have to make a change. Do you have examples...
A summary of things that we discussed in the maintainers meeting: - [ ] Maybe rename `pip_parse` to something else. - [ ] What do we do with `gazelle`? Do...
Right now you need to use the gazelle directive to tell gazelle how to resolve a particular proto import, it does not happen automatically.
If I were starting to look into this I would first - look at what bazel-gazelle does for go proto library management (if I remember correctly there is an if...
I was closing all proto related issues with the move of the py_proto_library out from the rules_python. Might have include an issue too many... So far no automatic discovery of...