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 docs@python, eric.araujo, lars.gustaebel, nadeem.vawda
Date 2012-02-18.18:10:03
SpamBayes Score 5.5674626e-08
Marked as misclassified No
Message-id <1329588604.33.0.900412148835.issue14013@psf.upfronthosting.co.za>
In-reply-to
Content
I think this is a reasonable proposal. I think it is good style to let tarfile figure out which supported compression methods are available instead of shutil or the user. So far I have no objections.

Following 3.3's crypt module, I think the name `methods' is superior to `formats' (maybe `compression_methods' is even better). Also, crypt's concept of a sorted list from stronger to weaker could also make sense here: ["xz", "bz2", "gz"]. Why not?
History
Date User Action Args
2012-02-18 18:10:04lars.gustaebelsetrecipients: + lars.gustaebel, nadeem.vawda, eric.araujo, docs@python
2012-02-18 18:10:04lars.gustaebelsetmessageid: <1329588604.33.0.900412148835.issue14013@psf.upfronthosting.co.za>
2012-02-18 18:10:03lars.gustaebellinkissue14013 messages
2012-02-18 18:10:03lars.gustaebelcreate