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 rpointel
Recipients petri.lehtinen, pitrou, rpointel, vstinner
Date 2011-11-03.08:19:50
SpamBayes Score 2.3687014e-06
Marked as misclassified No
Message-id <1320308391.67.0.880039141725.issue13326@psf.upfronthosting.co.za>
In-reply-to
Content
> According to the man page, find -print0 and xargs -r are also GNU extensions. Even though they work on OpenBSD (do they?), they could still break on some platforms.

Yes, it works fine, but you're allright.

> As find -exec cmd {} ';' is already used for everything but __pycache__, I'd rather only change the removal of __pycache__. I believe there are more files that match '*.py[co]' than '__pycache__', and people are already waiting for a separate rm process to be invoked on each *.py[co], so invoking a separate rmdir for each __pycache__ shouldn't make it much slower.

You mean to just exec rmdir instead of rm only for __pycache__?

Cheers,

Remi.
History
Date User Action Args
2011-11-03 08:19:51rpointelsetrecipients: + rpointel, pitrou, vstinner, petri.lehtinen
2011-11-03 08:19:51rpointelsetmessageid: <1320308391.67.0.880039141725.issue13326@psf.upfronthosting.co.za>
2011-11-03 08:19:51rpointellinkissue13326 messages
2011-11-03 08:19:51rpointelcreate