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 scoder
Recipients Arfrever, brett.cannon, christian.heimes, georg.brandl, lemburg, pitrou, rhettinger, scoder, tim.peters
Date 2014-11-06.18:59:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415300399.94.0.353557892875.issue22789@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, LZ4HC compression sounds like an obvious choice for write-once-read-many data like .pyc files to me. Blosc shows that you can achieve a pretty major performance improvement just by stuffing more data into less space (although it does it for RAM and CPU cache, not disk). And even if it ends up not being substantially faster for the specific case of .pyc files, there is really no reason why they should take more space on disk than necessary, so it's a sure win in any case.
History
Date User Action Args
2014-11-06 19:00:00scodersetrecipients: + scoder, lemburg, tim.peters, brett.cannon, georg.brandl, rhettinger, pitrou, christian.heimes, Arfrever
2014-11-06 18:59:59scodersetmessageid: <1415300399.94.0.353557892875.issue22789@psf.upfronthosting.co.za>
2014-11-06 18:59:59scoderlinkissue22789 messages
2014-11-06 18:59:59scodercreate