From: "Martin Ertsås" <martiert@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Chris Larson <clarson@kergoth.com>,
bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] utils: Use rm -rf in remove()
Date: Sat, 16 Feb 2013 14:51:02 +0100 [thread overview]
Message-ID: <511F8EC6.1080201@gmail.com> (raw)
In-Reply-To: <1360944017.31795.1.camel@ted>
On 02/15/13 17:00, Richard Purdie wrote:
> On Thu, 2013-02-07 at 18:08 -0700, Chris Larson wrote:
>> On Thu, Feb 7, 2013 at 4:55 PM, Richard Purdie
>> <richard.purdie@linuxfoundation.org> wrote:
>> - shutil.rmtree(name)
>> + # shutil.rmtree(name) would be ideal but its
>> too slow
>> + subprocess.call('rm -rf %s' % path,
>> shell=True)
>>
>> This is a good idea, but I'm curious about forking off a shell process
>> for it. I'd think this would work as well: subprocess.call(['rm',
>> '-rf', path])
> path can have wildcards in it. The code wasn't entirely obvious so I've
> tweaked it after your/Peter's comments. I'm hoping it will help the
> problems Martin was seeing too.
>
> Cheers,
>
> Richard
>
>
I think this is a good idea as well. One thing I would question though,
is to have this in the except clause. Why not:
for name in glob.glob(path):
try:
if recurse and os.path.isdir(path):
subprocess.call('rm -rf %s' % path, shell=True)
return
os.unlink(name)
except OSError as exc:
if exc.errno != errno.ENOENT:
raise
Personally I feel it is cleaner to have all the remove possibilities in
the try, and let the exceptions be in except. Kind of feel it is wrong
to let the recursive case be handled in the exception, as I don't see it
being an exceptional case to delete a folder.
Also, unfortunately your patch would not fix osx, as EISDIR is not the
error that is returned there. What I get is either a EPERM or an EACCES
(not on a mac now, so can't check it until monday). So osx would still
fall through to the raise.
next prev parent reply other threads:[~2013-02-16 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 23:55 [PATCH] utils: Use rm -rf in remove() Richard Purdie
2013-02-08 1:08 ` Chris Larson
2013-02-15 16:00 ` Richard Purdie
2013-02-16 13:51 ` Martin Ertsås [this message]
2013-02-16 14:54 ` Richard Purdie
2013-02-16 15:27 ` Martin Ertsås
2013-02-08 13:47 ` Peter Kjellerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511F8EC6.1080201@gmail.com \
--to=martiert@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.