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 insomniacslk
Recipients insomniacslk
Date 2017-07-24.21:05:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500930321.52.0.338757047173.issue31020@psf.upfronthosting.co.za>
In-reply-to
Content
Tarfile would benefit from exposing custom compressors. At the moment the only way to use something that is not gzip/bzip/lzma is to separate the archiving and compression steps.

A possible approach is to pass a custom compression function to `tarfile.TarFile.open`. However the current interface is not clean enough to be exposed. I have made a very conservative change via a pull request on GitHub, see https://github.com/python/cpython/pull/2734 . Some additional considerations can be found there.

A further step could require a simplified interface that only involves file name, file-like object and compression level, and returns a file-like object to read the compressed data from. For example:

def my_compressor(name, fileobj=None, compresslevel=9):
    # compression happens here
    return filelike_object


This further step is not captured in the pull request, but I can iterate and update the diff.
History
Date User Action Args
2017-07-24 21:05:21insomniacslksetrecipients: + insomniacslk
2017-07-24 21:05:21insomniacslksetmessageid: <1500930321.52.0.338757047173.issue31020@psf.upfronthosting.co.za>
2017-07-24 21:05:21insomniacslklinkissue31020 messages
2017-07-24 21:05:21insomniacslkcreate