We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looking at this code: https://github.com/celery/py-amqp/blob/master/amqp/transport.py#L364-L366 I understand that socket.timeout() would be raised in 2 cases:
Wouldn't it be better if client code can distinguish between the 2 scenarios ?
The text was updated successfully, but these errors were encountered:
what better approach are you suggesting?
Sorry, something went wrong.
How about raising socket.timeout() for EAGAIN and re-raise socket.error for EINTR ?
lets discuss a more detail of it here https://groups.google.com/forum/#!forum/celery-users
No branches or pull requests
Looking at this code: https://github.com/celery/py-amqp/blob/master/amqp/transport.py#L364-L366 I understand that socket.timeout() would be raised in 2 cases:
Wouldn't it be better if client code can distinguish between the 2 scenarios ?
The text was updated successfully, but these errors were encountered: