Well… that’s ultimately the implementer’s responsibility, but I view __fspath__
as a light-weight, side-effect free inquiry. If it’s necessary to do a background copy to return a local filesystem path, then perhaps you shouldn’t implement __fspath__
at all, and instead let the user open the file (or a middle layer) explicitly for reading.
1 Like