| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow these steps to rectify the issue:
Thanks again to your contribution and we look forward to looking at it! |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the PR. The new json.COMPACT constant needs to be documented in Doc/library/json.rst (and please add a .. versionadded:: 3.7 marker)
Sorry, something went wrong.
|
@berkerpeksag thanks! just added documentation for json.COMPACT |
Sorry, something went wrong.
There was a problem hiding this comment.
"could be used" -> "can be used"
Sorry, something went wrong.
There was a problem hiding this comment.
A constant that can be used as the *separators* argument to emit a compact serialization.
Sorry, something went wrong.
There was a problem hiding this comment.
+1 to Brett's suggestion.
Sorry, something went wrong.
There was a problem hiding this comment.
Please update the "Compact encoding" example at the top of the page.
Sorry, something went wrong.
There was a problem hiding this comment.
Also, following the style used in Doc/library/json.rst would be better:
.. versionadded:: 3.7
Instead of ``(',', ':')`` constant ``json.COMPACT`` could be used.
Sorry, something went wrong.
There was a problem hiding this comment.
versionchanged would be more appropriate here.
Sorry, something went wrong.
There was a problem hiding this comment.
``json.COMPACT`` -> :data:`json.COMPACT`
Sorry, something went wrong.
There was a problem hiding this comment.
+1 to Brett's suggestion.
Sorry, something went wrong.
|
@berkerpeksag @brettcannon thanks! I've just updated PR according to changes you requested. |
Sorry, something went wrong.
There was a problem hiding this comment.
Please also update JSONEncoder documentation at https://docs.python.org/3/library/json.html#json.JSONEncoder and add a test that passes separators=json.COMPACT to JSONEncoder. Sorry, I missed this in my earlier review.
Sorry, something went wrong.
There was a problem hiding this comment.
compact -> COMPACT
Sorry, something went wrong.
There was a problem hiding this comment.
Please wrap lines at 80 chars.
Sorry, something went wrong.
|
thanks @berkerpeksag ! I've just added changes corresponding to JSONEncoder |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## master #72 +/- ##
==========================================
+ Coverage 82.38% 82.38% +<.01%
==========================================
Files 1428 1428
Lines 351138 351147 +9
==========================================
+ Hits 289282 289294 +12
+ Misses 61856 61853 -3Continue to review full report at Codecov.
|
Sorry, something went wrong.
There was a problem hiding this comment.
I don't think a versionchanged field is necessary as nothing about the function actually changed. I think it would be better to update the paragraph above from "To get the most compact JSON representation,
you should specify (',', ':') to eliminate whitespace." to "To get the most compact JSON representation,
you should specify :attr:json.COMPACT to eliminate whitespace.
Sorry, something went wrong.
There was a problem hiding this comment.
@brettcannon sounds reasonable! I've just updated it, thanks!
Sorry, something went wrong.
|
@berkerpeksag @brettcannon any conclusion on this? :) |
Sorry, something went wrong.
|
@andrewnester I've been waiting for the discussion of https://bugs.python.org/issue29540 to settle down and be resolved before commenting further. |
Sorry, something went wrong.
|
@brettcannon looks like discussion stopped here https://bugs.python.org/issue29540 .. |
Sorry, something went wrong.
|
@andrewnester I just pinged the issue to explicitly see what people think about your attribute proposal. |
Sorry, something went wrong.
|
I opened bpo-29863 to finalize the discussion of the constant since I think it got lost on the older issue that proposed a new compact argument to json.dump(). |
Sorry, something went wrong.
|
@brettcannon thanks! is there any link to discussion or some mailing list? |
Sorry, something went wrong.
Sorry, something went wrong.
|
@andrewnester I just wanted to say sorry for the delay on making a decision for this. As I'm sure you have noticed on the issue it's basically split down the middle as to whether this PR should be accepted or not and so no one has made the final call. |
Sorry, something went wrong.
|
Closing this since I just closed the issue. |
Sorry, something went wrong.
…sole Refactor termios stuff in unix console
…n#72) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Fix for https://bugs.python.org/issue29540
I decided to go with Alternative version provided R.David Murray just to keep things simple