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
Decide the fate of undocumented script behavior of some modules #93096
Labels
docs
Documentation in the Doc dir
tests
Tests in the Lib/test dir
type-feature
A feature request or enhancement
Comments
|
@ericvsmith Thank you, I've added it to the list. |
This was referenced Jun 24, 2022
corona10
pushed a commit
that referenced
this issue
Jul 2, 2022
corona10
pushed a commit
that referenced
this issue
Jul 2, 2022
miss-islington
pushed a commit
that referenced
this issue
Jul 25, 2022
This PR couples with python/pyperformance#222 and supersedes #92560. Inspired by #93096 (comment). Automerge-Triggered-By: GH:ericsnowcurrently
arhadthedev
added a commit
to arhadthedev/cpython
that referenced
this issue
Aug 1, 2022
arhadthedev
added a commit
to arhadthedev/cpython
that referenced
this issue
Aug 1, 2022
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
tests
Tests in the Lib/test dir
type-feature
A feature request or enhancement
arhadthedev commentedMay 23, 2022
•
edited
There are three dozens of standard modules that can be called via
python -m
and their documentation doesn't mention it. They can be grouped into five categories:We need to decide what to do with all these undocumented categories.
I propose the following:
test
module with deduplicationCommand-Line Usage
into the docs like in https://docs.python.org/3/library/ast.html#command-line-usage or https://docs.python.org/3/library/trace.html#command-line-usageThe text was updated successfully, but these errors were encountered: