8eaf813984
Currently 'Subscription' class catches ConflictError inside and prints text 'The subscriber has been existed already.'. This is not good for two reasons: 1. The library user(program) wants to handle this exception by himself using convenient try/except mechanism along with many other exceptions that can happen during subscription creation. 2. The library user might not want some text to be printed in this situation by python-zaqarclient. For now this is the only situation when python-zaqarclient prints something when it is used as library. This patch makes "Subscription" class not to handle ConflictError exception by itself. And creates functional and unit tests to assert that this behavior is raised, when Zaqar returns 409 response code on subscription creation. In the future it would be good to list all exceptions that can be raised by the "Client" class's methods in their docstrings. See "zaqarclient/queues/v1/client.py" and "zaqarclient/queues/v2/client.py". Also it would be good if "Pool" and "Flavor" classes would throw ConflictError exception too. Closes-Bug: 1542780 Change-Id: I17c0e32a3dabec8303b3055a0d97db857d947b34 |
||
|---|---|---|
| .. | ||
| v1 | ||
| v2 | ||
| __init__.py | ||
| cli.py | ||
| client.py | ||