Nd2(SO4)3

I think in case the developer uses the library wrong ("breach of contract") it should throw an exception so one can't ignore it. Although printing wouldn't be that problematic in...

How about adding the reason of failure to each broker tuple in the the exception message? ``` Could not connect to any of the provided brokers: [("localhost",5672, "Connection refused")] ```...

I know, but printing is mostly useless anyway because it won't reach the user in a lot of setups (for example if you do logging via syslog + use `daemonize`...

Works nicely, thank you very much. Not sure what's the right approach. I hate exceptions, but loads of handlers could get messy as well. Maybe it would also make sense...

Is there a solution/workaround yet? I'd need slices to be zeroed before values are written into (but only if this field should be updated/values are set).

Any more thoughts on this? In my opinion probably everyone expects an array/slice to be zeroed before update... Partial update of an array seems to be a very rare edge...

Follow-up almost two years later: @ret is correct, If you want the simple\* and postgres libraries to be really free the code should be BSD{2,3}/MIT/Apache licensed. LGPL is a huge...

I see. Could be a bit of a problem: connecting takes nearly up to a minute sometimes (is that a Twitter API problem or one of the package? Seems a...

Yeah, pretty sure now that it's always happening before an EOF.

Read timeout is working fine. The `client.Follow(id)` is blocking very long - but returns without error. Not sure how I can test that.