Nick Lee

Not sure they are related, but your issue rings a bell of #239 and #242. Someone there suggested some workarounds. Other than that, I am sorry I can't suggest anything...

Sorry, I'd say no, mainly because I don't want to take care of one more framework. Thanks for the work though. It's good for telepot to embrace more situations, but...

@xen, after reading over your message a few times, I start to understand what you are trying to get at. I did misunderstand your intention a little bit. Your modification...

As I have indicated [here](https://github.com/nickoala/telepot/issues/408#issuecomment-409827643), I have decided to stop enhancing telepot because I want to spend time pursuing other interests. That said, I want to re-iterate that I appreciate...

I haven't tried it, but suspect Telegram will give you an error. Having written out the code, why don't you try it yourself? :blush:

You are correct. I didn't really solve the problem there. In any case, it will be fixed in the next release, whenever that will be.

That problem that you mentioned ( #87 ) was supposedly fixed by introducing a `retry` parameter in the connection pool (see my comment on Jul 26, 2016). Maybe your situation,...

I forgot which version it was, but somewhere between 7.1 and now, I introduced connection pooling, which is implemented in the module `telepot.api`. #87 happened right after connection pooling was...

One more thing. Before version 8.0 and connection pooling, I was using Requests. I didn't remember why I chose urllib3 over Requests for connection pooling ..... Maybe Requests did not...

I am actually considering making the underlying HTTP library configurable. That is, it allows you to switch between urllib3 and Requests. As I said, I did not see anything that...