Ignas Anikevicius
Ignas Anikevicius
I don't have bandwidth to work on this either.
One more reason why it may be a sub-optimal solution - sharing dependencies between different workspaces than have different requirements files can lead to unpredictable behaviour when two versions of...
@eaplatanios, one problem with the `//visibility:private` by default is that then users would need to manually annotate all of the new `BUILD.bazel` files they create with visibility settings which is...
None of the maintainers are actively working on Windows and contributions on fixing this would be greatly welcome!
Let me know if we can close this since #1784 got merged. i think that should address your use-case.
Since in file mode we don't want to name the targets by the package name (we would have clashes if for more than one py_library or py_binary, we would need...
In the BCR there is a patch that bumps the version to [the correct version](https://github.com/bazelbuild/bazel-central-registry/blob/a26099e5ffa366811cb82240881f5bdb7648d1ca/modules/rules_python/0.27.1/patches/module_dot_bazel_version.patch). Since we use automation to make releases, maintaining the version number manually would be something...
I am thinking that there is nothing we can do here and we should close the issue?
My concern is that it uses shutil.copyfile even though there was a comment that shutil.copyfile was not working under certain cirrumstances. It could be that the comment is wrong. I...
The CI should be happy again if you rebase. We had some issues when this PR was created, if I remember correctly.