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 loewis
Recipients georg.brandl, loewis, pitrou, rosslagerwall
Date 2010-12-22.20:16:54
SpamBayes Score 6.359077e-07
Marked as misclassified No
Message-id <1293049015.79.0.835484535656.issue10758@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think we can change this for the maintenance branches. The code behaves according to the documentation:

    access(path, mode) -> True if granted, False otherwise

"False otherwise" is really meant that way: otherwise. The specific condition is indeed not communicated. However, applications are entitled to not seeing exceptions come out of this function.

I would be in favor of changing this in the long term, but then raise exceptions in all cases. Alternatively, have it produce falsish values that encapsulate the error code.
History
Date User Action Args
2010-12-22 20:16:55loewissetrecipients: + loewis, georg.brandl, pitrou, rosslagerwall
2010-12-22 20:16:55loewissetmessageid: <1293049015.79.0.835484535656.issue10758@psf.upfronthosting.co.za>
2010-12-22 20:16:54loewislinkissue10758 messages
2010-12-22 20:16:54loewiscreate