When creating a daemon with a unix socket that has spaces in its file path, such as "/Users/samschott/Library/Application Support/myapp/myapp.sock" on macOS, registering a Pyro4 object fails with an "invalid uri" error.
This seems to happen because the regex which parses the uri does not allow whitespace in the location string. Is this behaviour intended or a bug?
When creating a daemon with a unix socket that has spaces in its file path, such as "/Users/samschott/Library/Application Support/myapp/myapp.sock" on macOS, registering a Pyro4 object fails with an "invalid uri" error.
This seems to happen because the regex which parses the uri does not allow whitespace in the location string. Is this behaviour intended or a bug?