Serpens66

> Yes, this is a valid request. Do you have a suggestion for what an "easy to use API" would look like from your perspective? thanks :) I'm not familiar...

Yes, sounds good. .. An advanced way for more customization, but only if this does not cost too much performance and is easy to implement for you: I previously used...

Make sure you also keep the different allowed usage per time in mind. Eg. at binance you have (if I understood documentation correct): 6100 per 5 minutes raw calls, 1200...

ah, this request is similiar to mine, while my suggested "merge_add" is superior, if it is possible to implement: https://github.com/xforce/anno1800-mod-loader/issues/65

I'm no expert regarding ssl and so on. I solved the problem like this in the connect function and it works (not 100% sure if it is a good solution)....

I used veersion 0.3.4 a long time without any problems. Then I thought it might be good to upgrade to 0.4.2 and did it... bad idea.. since then I'm missing...

> We could record how long it took to send the ping and reduce the wait accordingly. That would improve the behavior as long as sending the ping takes less...

> Your suggestion is also an option, however I don't like creating too many tasks at the library level. There's a long string of concurrency issues in this bug tracker......

> See the second example here: https://docs.python.org/3/library/asyncio-task.html#asyncio.wait_for there is only one example for "wait_for", so no clue what you mean by "second example". If you mean "asyncio.wait(..)" I don't think...

I created an issue: https://github.com/python/cpython/issues/96571 Maybe you can vouch for it, to make it more likely to happen. In the meantime you still may adjust sortedcontainers I guess? Just do...