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 eric.araujo
Recipients Claudiu.Popa, berker.peksag, brett.cannon, eric.araujo, lars.gustaebel, serhiy.storchaka
Date 2014-05-24.20:03:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400961828.47.0.490036931795.issue21550@psf.upfronthosting.co.za>
In-reply-to
Content
IIRC, when the tarfile module CLI was added, there was a decision to keep it short and simple, not mimic the whole tar(1) interface.

Python core ships with modules that should be featurefull, but we don’t put much focus or effort on general utilities: the only globally installed scripts are directly useful to Python devs (idle, pydoc, pyvenv, 2to3); the stdlib modules with a CLI are quick helpers (python -m SimpleHTTPServer) or smoke tests or demos IIRC; Tools/scripts have an even lower level of usefulness and maintenance.

I sympathize with the use case of finding missing pieces in tarfile, but I’m wary about the maintenance burden (code maintenance if it matches tar(1) fully, support if it does not, endless discussions about installing it on Windows like what happened for Tools/scripts/diff.py, etc).
History
Date User Action Args
2014-05-24 20:03:48eric.araujosetrecipients: + eric.araujo, brett.cannon, lars.gustaebel, Claudiu.Popa, berker.peksag, serhiy.storchaka
2014-05-24 20:03:48eric.araujosetmessageid: <1400961828.47.0.490036931795.issue21550@psf.upfronthosting.co.za>
2014-05-24 20:03:48eric.araujolinkissue21550 messages
2014-05-24 20:03:46eric.araujocreate