I've uploaded portalocker 3.1.1, which includes a patch that "fixes" this issue, where basically upstream just handles the error properly with a new exception. Quoting upstream [0]:
> That looks like the current "fix" is at least effective in that it throws the > correct exception now. > Beyond that I'm not sure what else I can do honestly. It appears that the > filesystem doesn't support read only locks for this case. > For cases like these I created the RedisLock that work across multiple > networked systems and is not limited by filesystems at all. > There's also a small chance that lockf as opposed to flock works in this case > it can be changed by overriding the LOCKER attribute: However, I'm going to let this bug open since the package still has problems supporting lock on NFS [0]: https://github.com/wolph/portalocker/issues/92#issuecomment-2179532676 -- josue
signature.asc
Description: PGP signature
