Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_python / 59783902f02f88397538aad359a25b43649011d1
commit59783902f02f88397538aad359a25b43649011d1[log] [tgz]
authorRichard Levasseur <rlevasseur@google.com>Mon Oct 14 21:29:57 2024 -0700
committerGitHub <noreply@github.com>Tue Oct 15 04:29:57 2024 +0000
tree50e21ee8ccfaffeaa161193a7212ca51e2de5d1f
parent595fe115023a8ce3edff6e8819938d82edc2b297 [diff]
fix(sphinxdocs),deps: allow using sphinx_stardoc with bzlmod; add stardoc 0.6.2 as dependency (#2295)

Using the sphinx_stardoc rule doesn't work with bzlmod because it refers
to the stardoc repo, which was a dev dependency. This means, even if a
user's root module has visibility to stardoc, rules_python doesn't.

To fix, make stardoc a non-dev dependency. With bzlmod semantics,
stardoc won't actually be loaded unless a user depends on it by using
sphinxdocs.

I ran into this while trying to port rules_testing over to sphinxdocs.
The pigweed project
recently started using sphinxdocs and didn't run into this problem, but
I'm pretty
sure that's because they're using workspace still, which doesn't have
the visibility
constraints that bzlmod does.
2 files changed
tree: 50e21ee8ccfaffeaa161193a7212ca51e2de5d1f
  1. .bazelci/
  2. .bcr/
  3. .ci/
  4. .github/
  5. docs/
  6. examples/
  7. gazelle/
  8. python/
  9. sphinxdocs/
  10. tests/
  11. third_party/
  12. tools/
  13. .bazelignore
  14. .bazelrc
  15. .bazelversion
  16. .git-blame-ignore-revs
  17. .gitattributes
  18. .gitignore
  19. .pre-commit-config.yaml
  20. .readthedocs.yml
  21. addlicense.sh
  22. AUTHORS
  23. BUILD.bazel
  24. BZLMOD_SUPPORT.md
  25. CHANGELOG.md
  26. CONTRIBUTING.md
  27. CONTRIBUTORS
  28. DEVELOPING.md
  29. internal_deps.bzl
  30. internal_setup.bzl
  31. LICENSE
  32. MODULE.bazel
  33. README.md
  34. version.bzl
  35. WORKSPACE
  36. WORKSPACE.bzlmod
README.md

Python Rules for Bazel

Build status

Overview

This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.

Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.

Examples live in the examples directory.

The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.

The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.

Documentation

For detailed documentation, see https://rules-python.readthedocs.io

Bzlmod support

  • Status: Beta
  • Full Feature Parity: No

See Bzlmod support for more details.