Skip to content

Web client and rtm client should be fully split, and web client should not use asyncio #633

@ryan-lane

Description

@ryan-lane

Description

The 2.x release of slackclient is completely unusable in projects not based on asyncio. The integration of asyncio is too deep into the library. Whether to use async or not in api calls should be up to the caller, not baked into the library. I've spent the last two weeks trying to upgrade my project based only on the web APIs, and so many things are broken that I believe I'm going to have to stay on 1.x forever, or look for a new library unless the asyncio code is removed.

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • testing related
  • discussion

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

slackclient version: 2.x

python version: 3.6+

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions