jerith (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} jerith) wrote, |
Sure, if I'm the one using Timeout. (I prefer not to, because it is known to be broken, but sometimes the breakage isn't critical and doing things properly is infeasible.)
The problem is that Timeout is often used by code I call, but didn't write. Thus, I must either catch the appropriate exception or find all occurrences and monkey-patch them. I do this in some of my code with protocol.rb so that I don't have to handle Timeout::Errors every time I make a network call. It's still pain I shouldn't have to suffer, though.
The problem is that Timeout is often used by code I call, but didn't write. Thus, I must either catch the appropriate exception or find all occurrences and monkey-patch them. I do this in some of my code with protocol.rb so that I don't have to handle Timeout::Errors every time I make a network call. It's still pain I shouldn't have to suffer, though.
