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 nadeem.vawda
Recipients Crispin.Wellington, Kontr-Olli, akuchling, dbonner, djc, eric.araujo, gkcn, loewis, nadeem.vawda, niemeyer, nirai, ozan.caglayan, pitrou, python-dev, r.david.murray, therve, thomaslee
Date 2011-10-02.21:46:37
SpamBayes Score 2.7949238e-09
Marked as misclassified No
Message-id <1317591998.92.0.34006048175.issue1625@psf.upfronthosting.co.za>
In-reply-to
Content
> This is all fine and well, but this is clearly a bug and not a feature.

No, it is not at all clear that this is a bug. I agree that this is a desirable
capability to have, but nowhere does the module claim to support multi-stream files.
Nor is it an inherent feature of the underlying bzip2 library that we are failing
to expose to users.

> [...] python 2.x users will never be able to extract multiple-stream bz2 files.

Incorrect. It is perfectly possible to extract a multi-stream bz2 file in 2.x -
you just need to open it with open() and decompress the data using
BZ2Decompressor (pretty much the same way that 3.3's BZ2File does it).

If there is really a large demand for these facilities in 2.x, I would be willing
to port 3.3's BZ2File implementation to 2.x and make it available on PyPI. But 
this patch is not going in to the 2.7 stdlib; it is simply not the sort of
behavior change that is acceptable in a bugfix release.
History
Date User Action Args
2011-10-02 21:46:39nadeem.vawdasetrecipients: + nadeem.vawda, loewis, akuchling, niemeyer, pitrou, therve, thomaslee, djc, eric.araujo, nirai, r.david.murray, dbonner, ozan.caglayan, Kontr-Olli, python-dev, gkcn, Crispin.Wellington
2011-10-02 21:46:38nadeem.vawdasetmessageid: <1317591998.92.0.34006048175.issue1625@psf.upfronthosting.co.za>
2011-10-02 21:46:38nadeem.vawdalinkissue1625 messages
2011-10-02 21:46:37nadeem.vawdacreate