[issue10758] posix_access swallows all errors

2010-12-22 Thread Martin v . Löwis
Martin v. Löwis added the comment: 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 indee

[issue10758] posix_access swallows all errors

2010-12-22 Thread Antoine Pitrou
Antoine Pitrou added the comment: The list of errnos indicating missing access seems open-ended. Things such as: [ENAMETOOLONG] The length of a component of a pathname is longer than {NAME_MAX}. [ENOENT] A component of path does not name an existing file or path is an empty string. [EN

[issue10758] posix_access swallows all errors

2010-12-22 Thread Ross Lagerwall
Changes by Ross Lagerwall : -- nosy: +rosslagerwall ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue10758] posix_access swallows all errors

2010-12-22 Thread Georg Brandl
New submission from Georg Brandl : access(2) can return errnos that correspond to input errors or general system faults, such as EINVAL, EIO or ENOMEM. In this case, an exception should be raised instead of returning False. It is probably best to whitelist those errnos that indicate missing a