Python-slack-sdk: PEP-541 Claim PyPI name `slack`

[1oglop1]

Hello, over the years slack has become a well known entity and installing it's client naturally falls to pip install slack.
However, current slack on PyPI has nothing in common slackclient or anything related to Slack.

I'd like a slack to be either primary or a redirect to slackclient.
Because it doesn't make much sense to do pip install slackclient and then from slack import WebClient because it would directly conflict with zweifisch/slack

https://pypi.org/project/slack/ - https://github.com/zweifisch/slack

The project looks abandoned / unmaintained since the last update was 7 years ago.

According to PEP-541 There are several options to claim a name on PyPI. https://www.python.org/dev/peps/pep-0541/#how-to-request-a-name-transfer

If the author won't respond it is possible to create a support request via GitHub issue.

[seratch]

Hi, thanks for the suggestion! Yes, the confusion around PyPI project names is a well-known issue.

In the near future, we are going to release v3 of this SDK. In the major version, we will be changing the project name from slackclient to slack_sdk (technically slack-sdk also works). The major reasons for this decision are to have broader feature sets (e.g., OAuth flow supports, interactivity features) and to make the names clearer and more consistent.

We are sorry for the inconvenience due to the renaming of the PyPI project and its module names (from slack to slack_sdk). We'll be working on the migration guide soon. If you're interested in how v3 looks like, the alpha versions are already available as below:

• https://github.com/slackapi/python-slackclient/tree/v3.0.0a4
• https://pypi.org/project/slack-sdk/

That said, we, this project team, should definitely seek the possibility of the name transfer to eliminate the confusion among slackclient v2.x users. We will be working on this process later on.