ask/kombu — pull request #77 by toofishes (2011-11-02 18:05:35+00:00)
Title: Connection tests and max_retry changes

These commits add some tests for previously uncovered code, namely the parse_url related stuff as well as the two methods that take max_retries- connection.ensure_connection and connection.ensure.

These lead into the final commit where we make max_retries able to take 0 as a valid value, and not treat it the same as the default (None). Why? Especially when running tests, namely those from celery, we should not be wasting time on retries when we cannot contact the message broker- we should just be failing immediately.