📖 DOCS: Improve constants representations #1603
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #1602 on why it can't be eg
td.C_O
instead oftd.constants.C_0
due to the way that sphinx reads the docstrings. Unless we move all the docstrings into the top init pys, it works like this. I had an attempt to sort this before and it is very sphinx internal configuration. Hopefully with the custom extension all this internal build representations are things we will be able to control and represent nicer.