FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

bpo-41762: Fix usage of productionlist markup in the doc by vstinner · Pull Request #22281 · python/cpython · GitHub

/ cpython Public

bpo-41762: Fix usage of productionlist markup in the doc - #22281

Merged
vstinner merged 3 commits into
python:masterfrom
vstinner:production_list
Sep 18, 2020
Merged

bpo-41762: Fix usage of productionlist markup in the doc#22281
vstinner merged 3 commits into
python:masterfrom
vstinner:production_list

Conversation

vstinner commented Sep 16, 2020
edited by bedevere-bot
Loading

Copy link
Copy Markdown
Member

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

Copy link
Copy Markdown
Member Author

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

Comment thread Doc/reference/toplevel_components.rst Outdated

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This change breaks the link to stmt_list.

Should we use the same identifier here, in expressions, simple statements and compound statements?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Yeah, I think that is a good idea (to preserve those links). Is there any other missing links between sections?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Or maybe use the least amount of namespaces possible?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I didn't check all modified pages.

corona10 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@vstinner @pablogsal

I can check my PR works well after this PR is merged :)
#22198

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.

Copy link
Copy Markdown
Member Author

Copy link
Copy Markdown
Member Author

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.

vstinner merged commit 8af239e into python:master Sep 18, 2020

Copy link
Copy Markdown
Contributor

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9.
🐍🍒⛏🤖

vstinner deleted the production_list branch September 18, 2020 07:10

Copy link
Copy Markdown
Contributor

Sorry @vstinner, I had trouble checking out the 3.9 backport branch.
Please backport using cherry_picker on command line.
cherry_picker 8af239eacfcf52e4e0e2b0223e7cea4672309483 3.9

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 18, 2020
)

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>

Copy link
Copy Markdown

GH-22300 is a backport of this pull request to the 3.8 branch.

Copy link
Copy Markdown
Contributor

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 18, 2020
)

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>

Copy link
Copy Markdown

GH-22301 is a backport of this pull request to the 3.9 branch.

miss-islington added a commit that referenced this pull request Sep 18, 2020
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>
vstinner added a commit that referenced this pull request Sep 18, 2020
…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>
ambv pushed a commit to ambv/cpython that referenced this pull request Oct 4, 2020
)

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>
xzy3 pushed a commit to xzy3/cpython that referenced this pull request Oct 18, 2020
)

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".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation in the Doc dir skip news

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants


Back | FazBrowse Home | New Git URL