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 eric.smith
Recipients eric.smith, liad100, rushter
Date 2018-08-22.11:32:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534937572.89.0.56676864532.issue34393@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not asking to be difficult, I'm asking because a full specification would be required in order to implement this.

For example, you're excluding the "compresslevel" parameter, so presumably you'd want the default of 9, which is the slowest option. I'm not sure this is a good idea. Shouldn't the caller be able to specify this? If not, why not?

In any event, I think the best thing to do is to let the caller use any compression they want, and allow them full control over the compression parameters.

Unless, of course, there's any documented standard for json compression (even a de facto standard would be interesting to know about).
History
Date User Action Args
2018-08-22 11:32:52eric.smithsetrecipients: + eric.smith, rushter, liad100
2018-08-22 11:32:52eric.smithsetmessageid: <1534937572.89.0.56676864532.issue34393@psf.upfronthosting.co.za>
2018-08-22 11:32:52eric.smithlinkissue34393 messages
2018-08-22 11:32:52eric.smithcreate