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 sushisource
Recipients Jovik, ivan.radic, paul.moore, python-dev, r.david.murray, sushisource, tim.golden, zach.ware
Date 2014-10-16.16:58:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413478723.65.0.474391517807.issue19643@psf.upfronthosting.co.za>
In-reply-to
Content
Although this is closed, I stumbled across it while looking to see if this behavior had changed at all recently, and I have a suggestion I think might work.

How about we take Tim's example error function which was added to the docs, and it's bound to something like shutil.REMOVE_WINDOWS_READONLY, so it can be used in the following way (probably with a better name):

shutil.rmtree("C:/readonlyfilesinhere", onerror=shutil.REMOVE_WINDOWS_READONLY)

Good idea? Too weird?
History
Date User Action Args
2014-10-16 16:58:43sushisourcesetrecipients: + sushisource, paul.moore, tim.golden, r.david.murray, python-dev, zach.ware, Jovik, ivan.radic
2014-10-16 16:58:43sushisourcesetmessageid: <1413478723.65.0.474391517807.issue19643@psf.upfronthosting.co.za>
2014-10-16 16:58:43sushisourcelinkissue19643 messages
2014-10-16 16:58:43sushisourcecreate