RetroSearch Browse

Wed Jun 27 15:10:33 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-June/120800.html

On 27/06/12 02:19:03, Giampaolo Rodolà wrote:
> 2012/6/27 Cameron Simpson <cs at zip.com.au>:
>> So I'd be +0.5 for making the docs more clear that True is reliable and
>> False may merely mean "could not access".
> 
> +1

+1

> I was about to propose a 'strict' parameter which lets the exception
> propagate in case of errno != EACCES/EPERM but a doc fix is probably
> just fine.
> I'll file a bug report later today.

A 'strict' parameter that just propagates the exception might be a
good idea.  That would allow the user to deal with whatever issues
stat() encounters.

Arbitrarily mapping EPERM to 'False' would be unhelpful, as it leaves
the user in a position where one value can mean two different things.

-- HansM

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/120800.html below:

[Python-Dev] os.path.exists() / os.path.isdir() inconsistency when dealing with gvfs directories