When raising ZMQError: Permission denied it would be helpful if context were given #1287
I recently received this traceback:
It turned out that it was unable to create
Could we make it so that the error includes info about what it was getting permission denied on? Something like this would have been helpful:
The text was updated successfully, but these errors were encountered:
That would indeed be great! It might be difficult, though, because we don't have path information in the underlying error. All we have is that it was EPERM.
To do this, I think we'd need to special-case error handing in bind/connect and re-raise a new error:
# pseudo-ish code try: ... except ZMError as e: if EPERM and url.startswith('ipc://'): raise ZMQError(EPERM, message=message_with_url)