Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Public usage of sphinxdocs #1796

Answered by aignas
castler asked this question in Q&A
Mar 12, 2024 · 3 comments · 1 reply
Discussion options

Hi,

I was looking at https://github.com/agoessling/rules_sphinx to move it to bzlmod.

While doing so I figured out that the sphinx integration implemented by rules_python is way more advanced (and feature complete). I get some mixed signals when looking at sphinxdocs though. While it seems there is a public part, it cannot be all used publicly. Since https://github.com/bazelbuild/rules_python/blob/main/sphinxdocs/private/BUILD.bazel#L37 is only visible within rules_python and not publicly.

So my question is: is it intended and sphinxdocs shall not be used by users of rules_python?

Thanks!

You must be logged in to vote

The main intention was to not expose an API prematurely. I personaly would love to see this reused in other projects and rules_testing could use this too.

I think if you would be willing to give us feedback on what works and what doesn't and potentially help by contributing PRs if you have the time/willingness, then it would be definitely very appreciated.

But befare deciding on how we proceed, let's see what @rickeylev has to say.

Replies: 3 comments · 1 reply

Comment options

The main intention was to not expose an API prematurely. I personaly would love to see this reused in other projects and rules_testing could use this too.

I think if you would be willing to give us feedback on what works and what doesn't and potentially help by contributing PRs if you have the time/willingness, then it would be definitely very appreciated.

But befare deciding on how we proceed, let's see what @rickeylev has to say.

You must be logged in to vote
0 replies
Answer selected by castler
Comment options

Sure! First usage was really pleasant!

I will test it a little more for our use-cases and can provide either feedback here or in form of issues (what you guys prefer).

You must be logged in to vote
0 replies
Comment options

Yeah, I'm fine with exposing it publicly as an unsupported/experimental API. I want to move rules_testing over to it, too. We can change those visibility settings to public and add some doc disclaimers about them.

the sphinx integration implemented by rules_python is way more advanced (and feature complete).

Thanks 😁!

What language(s) are you generating docs for?

You must be logged in to vote
1 reply
@castler
Comment options

Yeah, I'm fine with exposing it publicly as an unsupported/experimental API. I want to move rules_testing over to it, too. We can change those visibility settings to public and add some doc disclaimers about them.

OK. I will prepare a PR.

What language(s) are you generating docs for?

We mainly use Sphinx to generate higher-level documentation (e.g. user-documentation, how-to guides, ...). But we also have C++ and Python code, but honestly did not yet generate docs for it with thinks. That might be a next interesting step!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.