-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Allow "-m json" instead of "-m json.tool" #122873
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
Comments
The "No warning" branch looks good to me (it would just need docs and News for me to approve a PR) |
Hi @hugovk! Just a quick note: |
Agreed. And change this in def main():
- prog = 'python -m json.tool'
+ prog = 'python -m json' @treyhunner Would you like to put together a PR? |
I will put together a PR shortly. 👍 |
+1 from me |
PR is here: #122884 |
Co-authored-by: Adam Turner <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]> Co-authored-by: Alyssa Coghlan <[email protected]>
Co-authored-by: Adam Turner <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]> Co-authored-by: Alyssa Coghlan <[email protected]>
Feature or enhancement
Proposal:
This is a feature proposal for allowing
python3 -m json
to work in addition topython -m json.tool
and softly deprecating the use ofpython3 -m json.tool
.I made a branch to see what these changes might look like.
Here is a separate branch which issues a
DeprecationWarning
.However, since
json.tool
will continue working that warning may cause more hassle for end users than is worthwhile.I think the no-warning approach may be more sensible.
Has this already been discussed elsewhere?
I have already discussed this feature proposal on Discourse
Links to previous discussion of this feature:
Discussion in Ideas discuss thread
Linked PRs
The text was updated successfully, but these errors were encountered: