On 27/06/12 02:19:03, Giampaolo Rodolà wrote: > 2012/6/27 Cameron Simpson <c...@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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com