This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author phr
Recipients phr, serhiy.storchaka
Date 2020-05-14.11:17:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589455078.68.0.516083802375.issue40623@roundup.psfhosted.org>
In-reply-to
Content
It's coming back to me, I think I used the no-separator format because I made the multi-document input files by using json.dump after opening the file in append mode.  That seems pretty natural.  I figured the wikipedia article and the json.tool patch just released were evidence that there is interest in this.  The approach of writing newlines between the docs and iterating through lines is probably workable though.  I don't know why I didn't do that before.  I might not have been sure that json docs never contain newlines.

Really it would be nice if json.load could read in anything that json.dump could write out (including with the indent parameter), but that's potentially more complicated and might conflict with the json spec.
History
Date User Action Args
2020-05-14 11:17:58phrsetrecipients: + phr, serhiy.storchaka
2020-05-14 11:17:58phrsetmessageid: <1589455078.68.0.516083802375.issue40623@roundup.psfhosted.org>
2020-05-14 11:17:58phrlinkissue40623 messages
2020-05-14 11:17:58phrcreate