Split out //sphinxdocs
to be a separate bazel submodule and setup publishing to BCR
#2511
Labels
//sphinxdocs
to be a separate bazel submodule and setup publishing to BCR
#2511
It seems that having a non-dev dependency on
stardoc
means thatrules_python
is pulling in all of the transitive dependencies ofstardoc
and we may getrules_kotlin
in the closure. That is sub-optimal and could be improved, but needs help from someone willing to dedicate the time.List of things that would need to be done:
MODULE.bazel
to//sphinxdocs
folder.sphinx
related PyPI deps to thatMODULE.bazel
. Currentlydev_pip
hub repo has more than is needed by the docs only, I think.gazelle
is setup.WORKSPACE
setup (sphinxdocs_deps.bzl
andsphinxdocs_setup.bzl
Out of scope:
sphinx_bzl
Python library and its dependencies. This isn't solved today, so no need to block splitting out a separate module on this problem.Context: #2498
The text was updated successfully, but these errors were encountered: