Should fix #1599 by shifting to an EAFP approach to validating directory access.
File permissions validation still relies on os.access(), for now.
Checklist
[x] Updated HISTORY.rst and link to any relevant issue (if these changes are user-facing)
[n/a] Updated the user's guide (if needed)
[x] Tested the Workbench UI on macOS
[x] Tested the Workbench UI on Windows
macOS screenshots
Tested the Workbench UI on macOS with the following eight user permissions scenarios (some more likely to exist IRL than others): ---, r--, -w-, --x, rw-, r-x, -wx, rwx. Here are just a few examples:
No access (missing r, w, and x)
Strictly readonly (has r, missing w and x)
"Readonly" in the colloquial sense (has r and x, missing w)
Description
Should fix #1599 by shifting to an EAFP approach to validating directory access.
File permissions validation still relies on os.access(), for now.
Checklist
macOS screenshots
Tested the Workbench UI on macOS with the following eight user permissions scenarios (some more likely to exist IRL than others):
---,r--,-w-,--x,rw-,r-x,-wx,rwx. Here are just a few examples:No access (missing r, w, and x)
Strictly readonly (has r, missing w and x)
"Readonly" in the colloquial sense (has r and x, missing w)
Full access (has r, w, and x)