➜

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 ronron
Recipients bob.ippolito, enedil, rhettinger, ronron, serhiy.storchaka
Date 2018-09-02.08:26:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535876788.67.0.56676864532.issue34529@psf.upfronthosting.co.za>
In-reply-to
Content 
Well... when handling GBs of data - it's preferred to generate the file directly in the required format rather than doing conversions. 

The new line is a format... protocols don't matter here...
I still think the library should allow the user to create this format directly.

Lets get out of the scope of Google or others... The new line is a great format it allows you to take a "row" in the middle of the file and see it. You don't need to read 1gb file into parser in order to see it you can use copy 1 row... We are adopting this format for all our jsons, so it would be nice to get the service directly from the library.
History
Date User Action Args
2018-09-02 08:26:28ronronsetrecipients: + ronron, rhettinger, bob.ippolito, serhiy.storchaka, enedil
2018-09-02 08:26:28ronronsetmessageid: <1535876788.67.0.56676864532.issue34529@psf.upfronthosting.co.za>
2018-09-02 08:26:28ronronlinkissue34529 messages
2018-09-02 08:26:28ronroncreate