| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I checked manually the rendered HTML documentation: reference/expressions.html still contains clickable links between the different grammar items. For example, I can click on "expression" from lambda_expr and I'm pointed to expression definition of the "6.13. Conditional expressions" section. I also checked library/string.html: links are kept. cc @JulienPalard @deronnax @isidentical @pablogsal @lysnikolaou |
Sorry, something went wrong.
There was a problem hiding this comment.
This change breaks the link to stmt_list.
Should we use the same identifier here, in expressions, simple statements and compound statements?
Sorry, something went wrong.
There was a problem hiding this comment.
Yeah, I think that is a good idea (to preserve those links). Is there any other missing links between sections?
Sorry, something went wrong.
There was a problem hiding this comment.
Or maybe use the least amount of namespaces possible?
Sorry, something went wrong.
There was a problem hiding this comment.
I didn't check all modified pages.
Sorry, something went wrong.
Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier.
compound_stmts, expressions, simple_stmts and toplevel_components now use the "python-grammar" identifier for their "productionlist" markups.
|
Doc/reference/*.rst must all live in the same productionlist domain (same grammar):
Examples:
|
Sorry, something went wrong.
|
Ok, I pushed a 3rd commit. I checked links between reference/ documents and they all have been repaired by my 3rd commit. I'm going to merge this PR once the CI pass. |
Sorry, something went wrong.
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Sorry, something went wrong.
|
Sorry @vstinner, I had trouble checking out the 3.9 backport branch. |
Sorry, something went wrong.
) Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar". (cherry picked from commit 8af239e) Co-authored-by: Victor Stinner <vstinner@python.org>
|
GH-22300 is a backport of this pull request to the 3.8 branch. |
Sorry, something went wrong.
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Sorry, something went wrong.
) Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar". (cherry picked from commit 8af239e) Co-authored-by: Victor Stinner <vstinner@python.org>
|
GH-22301 is a backport of this pull request to the 3.9 branch. |
Sorry, something went wrong.
Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar". (cherry picked from commit 8af239e) Co-authored-by: Victor Stinner <vstinner@python.org>
…H-22300) Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar". (cherry picked from commit 8af239e) Co-authored-by: Victor Stinner <vstinner@python.org>
) Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar". (cherry picked from commit 8af239e) Co-authored-by: Victor Stinner <vstinner@python.org>
| Back | FazBrowse Home | New Git URL |
Use an unique identifier for the different grammars documented using
the Sphinx productionlist markup.
productionlist markups of the same grammar, like "expressions" or
"compound statements", use the same identifier.
https://bugs.python.org/issue41762