Message 61428 - Python tracker

➜

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	draghuram
Recipients	draghuram, georg.brandl, gvanrossum, ntkoopman
Date	2008-01-21.17:44:15
SpamBayes Score	0.047380153
Marked as misclassified	No
Message-id	<2c51ecee0801210944x1675a3ecx496089b75c95f5ee@mail.gmail.com>
In-reply-to	<1200934065.93.0.408554713353.issue1669@psf.upfronthosting.co.za>

Content
> and it should use the onerror() handling used for all other errors" > which makes sense for me too. Sure. I am ok with using 'onerror'. The point I am trying to make is that there is slight difference between 'onerror' in this case and in the three other places where it is called. In the case of symlink, rmtree() returns even when 'onerror' doesn't raise exception. This is not same in the other cases where rmtree() continues. I am just wondering if this inconsistency is worth it and if it is, an explicit mention in the doc will be nice.

> and it should use the onerror() handling used for all other errors"
> which makes sense for me too.

Sure. I am ok with using 'onerror'. The point I am trying to make is
that there is slight difference between 'onerror' in this case and in
the three other places where it is called. In the case of symlink,
rmtree() returns even when 'onerror' doesn't raise exception. This is
not same in the other cases where rmtree() continues. I am just
wondering if this inconsistency is worth it and if it is, an explicit
mention in the doc will be nice.

History
Date	User	Action	Args
2008-01-21 17:44:17	draghuram	set	spambayes_score: 0.0473802 -> 0.047380153 recipients: + draghuram, gvanrossum, georg.brandl, ntkoopman
2008-01-21 17:44:16	draghuram	link	issue1669 messages
2008-01-21 17:44:15	draghuram	create