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 twb
Recipients amaury.forgeotdarc, gregory.p.smith, ned.deily, r.david.murray, schmir, twb
Date 2009-10-01.20:13:19
SpamBayes Score 3.1204604e-06
Marked as misclassified No
Message-id <1254428002.97.0.400284149237.issue6972@psf.upfronthosting.co.za>
In-reply-to
Content
Even if we can't fix things for this release, presumably it's not too
late to fix things for 2.7, right?

Yes, there certainly are cases where you might want to have creative
usage of symlinks and stored paths to allow overwriting existing files,
and placing files outside of the extraction path, but that doesn't seem
like the default case to me. Would it be a decent compromise to add a
extract_under_path=True default option to extract() and extractall() for
2.7?
History
Date User Action Args
2009-10-01 20:13:23twbsetrecipients: + twb, gregory.p.smith, amaury.forgeotdarc, schmir, ned.deily, r.david.murray
2009-10-01 20:13:22twbsetmessageid: <1254428002.97.0.400284149237.issue6972@psf.upfronthosting.co.za>
2009-10-01 20:13:20twblinkissue6972 messages
2009-10-01 20:13:19twbcreate