homepage

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 mrts
Recipients mrts, pitrou
Date 2008年12月29日.08:46:04
SpamBayes Score 0.0003979254
Marked as misclassified No
Message-id <1230540365.94.0.963262339481.issue4489@psf.upfronthosting.co.za>
In-reply-to
Content
A blunt, ineffective solution would be to walk the tree before removing
it and recording path : inode pairs in a dict on first pass and then
checking that the inodes have not changed during removal on second pass.
If no clever bulletproof fix emerges, perhaps this should be added as
shutil.rmtree_safe (duh, API bloat...)?
History
Date User Action Args
2008年12月29日 08:46:06mrtssetrecipients: + mrts, pitrou
2008年12月29日 08:46:05mrtssetmessageid: <1230540365.94.0.963262339481.issue4489@psf.upfronthosting.co.za>
2008年12月29日 08:46:05mrtslinkissue4489 messages
2008年12月29日 08:46:04mrtscreate

AltStyle によって変換されたページ (->オリジナル) /