jpiper

Reverting to 2.2.0 has fixed the issue so I assume this is a regression introduced in 2.3.0

> > I can confirm this as well, combined with the very low value of retry.backoff.max.ms (1s) the latest version of librdkafka can easily turn into a DDOS cannon at...

> ... until one of their connections has an intermittent error in the middle of the night and their cluster gets melted :/ I feel seen

It actually appears that for this example, when you a terminal w

Maybe try with the latest release of 2.3.0 first

What do you think about finding a way to detect LLDB running and only do this in that scenario? I'm slightly worried that this could mask problems with `argv` imports...

It actually appears that lldb loads python with an `lldb` module which isn't usually around, so I think the following might be a good solution ``` try: from sys import...

I'll be looking at implementing this soon™, but clint is on the backburner for me and is effectively in "maintenance mode" whilst I wrap up my PhD, so I can't...

@kennethreitz mentions he'd like to move over to docopt, but this would mean the package would no longer be vendorable - thoughts?

I wonder if this is a popular feature? We could definitely add percentage to the optional arguments.