Message384597
An alternative would be to add a "strict" parameter that defaults to False. In non-strict mode, map all OSError exceptions to a False return value. In strict mode, use _ignore_error(e) to determine whether to return False or propagate the exception. The question then is whether to add ERROR_INVALID_NAME (123) to _IGNORED_WINERRORS since the error means the name can never exist. On the other hand, ERROR_ACCESS_DENIED due to a permission error would be propagated in strict mode -- because the path's existence is unknown. |
|
Date |
User |
Action |
Args |
2021-01-07 17:30:44 | eryksun | set | recipients:
+ eryksun, paul.moore, tim.golden, zach.ware, steve.dower, gaborjbernat, domdfcoding2 |
2021-01-07 17:30:44 | eryksun | set | messageid: <1610040644.84.0.270003892808.issue42855@roundup.psfhosted.org> |
2021-01-07 17:30:44 | eryksun | link | issue42855 messages |
2021-01-07 17:30:44 | eryksun | create | |
|