@bea well, new colleague is starting in january and IT guy is out sick and presumably she wants a computer that she can use (and no one will be here between tomorrow and january)
buffers[0].result_history[67] well, new colleague is starting in january and IT guy is out sick and presumably she wants a computer that she can use (and no one will be here between tomorrow and january)
@zatnosk it's real weird due to the global interpreter lock and all, which I suspect is the reason why the old code was sometimes not working as well as it should have. the new code is a lot better there.
@zatnosk nah, it is mostly for if you use multiple streams at once while also doing other stuff (with python threading). In any case, new code should be, worst case, as good as before. Mind, if you're below 1.2.0, you'll have to make some changes to your code.
@zatnosk@unrealestate if it's working, then there's no _real_ reason to upgrade - the change is mostly to make the streaming api not break a lot when threading is used (also two functions were ignoring the async parameter whoops)
Hey I pushed out a maintenance release for Mastodon.py. The changes in it are exclusively to the streaming API but they vastly improve its stability so upgrading is recommended if you use that (but remember that if you were on < 1.2.0 there were breaking changes in that)
your feedback and/or contributions to tootmage are now welcome (mind, still slightly painful to get to run while mastodon.py 1.2.1 is Not Yet Out, but still): https://github.com/halcy/tootmage