Rewriting the Slack Python SDK

It still amazes me that Slack, with its infinite resources, hasn’t built native clients. One code base is nice and all, but man I loathe the Electron app.

I was trying to update my all-in-one duct tape Docker image[0] yesterday and was surprised to see that they ramped up the complexity so much for this release, I had to install a new C library just to be able to compile a dependency of a dependency they added.[1]<p>[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;underyx&#x2F;url" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;underyx&#x2F;url</a><p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;underyx&#x2F;url#5-2019-05-31" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;underyx&#x2F;url#5-2019-05-31</a>

I&#x27;ve done the integration with 10+ different chat API&#x27;s, Slack is one of the most complicated ones and the one that ignored the whole industry at all. The way it is done is totally alien to any experience you might have with other chat sdk&#x27;s before.

Happy about this, writing a slack app&#x2F;bot with the old SDK was often opaque<p>sc.api_call() with strings for the specific API (there are dozens, each with different inputs) always felt like a temporary ducttape SDK

Don&#x27;t bother, I have my own based on asyncio with Real Time API support, pagination and everything. If people interested separating this to it&#x27;s own package, let me know!<p><a href="https:&#x2F;&#x2F;github.com&#x2F;kissgyorgy&#x2F;gerrit-slack-bot&#x2F;blob&#x2F;master&#x2F;slack.py" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kissgyorgy&#x2F;gerrit-slack-bot&#x2F;blob&#x2F;master&#x2F;s...</a>

They&#x27;re rewriting with py3 in mind?<p>Excellent, unlike removing a headphone jack; I consider this truly courageous.