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 lars.gustaebel
Recipients christian.heimes, edulix, lars.gustaebel, loewis, serhiy.storchaka
Date 2014-04-14.11:20:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397474409.44.0.835169918743.issue18321@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, let me tell you why I reject your contribution at this point.

The patch you submitted may be well-suited for your purposes but it does not meet the requirements of a standard library implementation because it is not generic and comprehensive enough.

It contains duplicate code, spelling mistakes and needless code changes e.g.  in test_tarfile.py.

It does not expose one set of volumes as one tar archive to the user. It is not possible to iterate over all members of all volumes in one go. It does not allow random-access.

Actually, it does not implement complete multivolume support but only the "easy" parts.  For example, it fails to read GNU tar archives that are split in the middle of a pax header block sequence. The other way around, when writing it makes a split only when it is inside the data part of a member. Hence, it is possible that a volume turns out smaller than max_volume_size which is not only inaccurate but also bad on a tape device.

If you decide that you still want multivolume support in tarfile, feel free to reopen this issue with a new and significantly better patch. I gave you a number of clues on what I think is required.
History
Date User Action Args
2014-04-14 11:20:09lars.gustaebelsetrecipients: + lars.gustaebel, loewis, christian.heimes, serhiy.storchaka, edulix
2014-04-14 11:20:09lars.gustaebelsetmessageid: <1397474409.44.0.835169918743.issue18321@psf.upfronthosting.co.za>
2014-04-14 11:20:09lars.gustaebellinkissue18321 messages
2014-04-14 11:20:08lars.gustaebelcreate