-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
bpo-13474 Add -m reference in context of code execution #6901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@ncoghlan, ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but needs a markup fix (I'm on my phone, or I'd fix it directly)
@@ -22,7 +22,7 @@ The following are blocks: a module, a function body, and a class definition. | |||
Each command typed interactively is a block. A script file (a file given as | |||
standard input to the interpreter or specified as a command line argument to the | |||
interpreter) is a code block. A script command (a command specified on the | |||
interpreter command line with the '**-c**' option) is a code block. The string | |||
interpreter command line with the '**-c**' option) is a code block. A module run as a top level script (as module `__main__`) from the command line using a '**-m**' argument is also a code block. The string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double backticks on the markup
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
(I am puzzled as to why me-of-a-year-ago didn't just fix that. Sorry for the delay...) |
Re-opened the PR here: #16045 |
Thanks @JulienPalard |
https://bugs.python.org/issue13474