You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im my opinion it would nice if the method does not raise any exception but return None in case of an error.
This would largely correspond to the C implementation, which returns -1 in case of error and 0 in case of success.
In my suggestion -1 would be None and 0 would be the name of the socket.
In my opinion, the compositor should be responsible for responding to an error, not pywayland.
Im my opinion it would nice if the method does not raise any exception but return
None
in case of an error.This would largely correspond to the C implementation, which returns
-1
in case of error and0
in case of success.In my suggestion
-1
would beNone
and0
would be the name of the socket.In my opinion, the compositor should be responsible for responding to an error, not pywayland.
See also https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/486 why it might make sense to try multiple socket names.
If the method does not raise any errors, the following implementation would be possible without catching a generic Exception:
The text was updated successfully, but these errors were encountered: