R. David Murray added the comment:
See issue 16333 for the bug report against the json trailing whitespace.
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9767
___
Georg Brandl ge...@python.org added the comment:
FWIW if something is fixed, it should be the json output. However, I can
imagine (without looking at the code) that this would mean a lot of special
casing.
--
___
Python tracker
New submission from Terry J. Reedy tjre...@udel.edu:
I ran doctest on LibRef 17.2 json saved as .txt. There are 4 failures: 2 are
clearly doc issues, the other 2 I do not know. I hope someone reads this who is
already familiar
DOC PATCHES
dumps(2 + 1j, cls=ComplexEncoder)
should be
Georg Brandl ge...@python.org added the comment:
r84481 should fix all except the whitespace one. I don't think this is worth
fixing; I will not add a trailing whitespace to the docs, and adding a
doctest: NORMALIZE_WHITESPACE directive does not help readability, especially
since nobody
Terry J. Reedy tjre...@udel.edu added the comment:
Well, anyone who does try that example will see the correct output and not
notice the trailing whitespace difference. It will only be an issue if and when
automated doc doctests are run repeatedly. Worry about it then. Thanks for the
quick
