slackapi / slackapi/bolt-python

Fully define dependencies for async support via optional dependency group

Open
#1,472 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area:async auto-triage-skip dependencies
Dominant language
Python
Stars
1.3k
Forks
288
Avg merge
1d 8h
Merged PRs (30d)
10

Description

The current docs suggest adding aiohttp as a dependency to create an async app, but this creates a direct dependency on aiohttp for consumers of slack-bolt on what is is really a transitive dependency for the consumer of slack-bolt. This is especially important because this leaves it to consumers to find compatible versions of slack-bolt and aiohttp without the aide of a package manager.

slack-bolt should define an optional dependency group and include aiohttp so that consumers of this library don't need to maintain a dependency on a transitive. Consumers would be able to uv add slack-bolt[async] for example to include the optional dependencies.

Category (place an x in each of the [ ])
  • slack_bolt.App and/or its core components
  • slack_bolt.async_app.AsyncApp and/or its core components
  • Adapters in slack_bolt.adapter
  • [] Others

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the documentation for slack_bolt.async_app.AsyncApp and the package metadata that defines dependencies. Check how async support is currently installed, then verify that the optional async dependency group includes aiohttp and that the documented uv add slack-bolt[async] workflow installs it without requiring consumers to manage it directly.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.