PR Review — docs: add Linux aiolimiter DBus workaround to setup guide

Nice, practical addition. This is exactly the kind of "silent failure" that wastes hours for new contributors.

What looks good:

• The note is placed right where the failure occurs (inline with make dev), which is the right spot
• Clear cause → symptom → fix flow
• Confirmed with before/after test runs — good validation

One suggestion:
Consider also mentioning PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring as an environment variable alternative:

PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring poetry install

This disables the keyring entirely and avoids the DBus error upfront, so users don't need the manual pip fix afterwards. Some distros have this as the recommended Poetry workaround. Worth a line if you want to offer a "prevention" path alongside the "fix" path.

Either way, this is a net improvement to the contributor experience. Happy to see it merged.

— Friday, AI assistant to @RichardAtCT

PR Review
Reviewed head: 1060d77c70bb129b4842e729947a95a248b09d51

Summary

• Documents a known Linux-specific Poetry/keyring issue that silently skips aiolimiter installation, causing 2 confusing test failures
• Adds two workaround options (env var or poetry config) plus a recovery path for users who already hit the problem
• Adds a trailing newline to the last line of the file

What looks good

• The workarounds are accurate and cover both the proactive and recovery cases
• Good callout that the error appears non-fatal but has a real downstream effect — that's the kind of trap that wastes hours

Issues / questions

1. [Nit] CONTRIBUTING.md — The recovery step suggests poetry run pip install aiolimiter rather than poetry add aiolimiter. Both work, but poetry add would persist it to pyproject.toml/poetry.lock properly. Worth noting if this is a development dependency that should actually live there (or just clarifying that pip install is intentionally temporary).

Suggested tests

• N/A — docs-only change

Verdict
✅ Ready to merge

— Friday, AI assistant to @RichardAtCT

Thanks for the thorough review! Regarding the poetry run pip install aiolimiter vs poetry add suggestion — aiolimiter is already declared as a dependency in pyproject.toml (via the python-telegram-bot[rate-limiter] extra). The issue is that Poetry silently skips installing it due to the DBus error, so poetry add would just update pyproject.toml unnecessarily. The pip install workaround is intentionally temporary — it just forces the already-declared package to actually land in the venv. Happy to add a clarifying comment in the docs if that would help.

Good point — that makes sense. Since is already declared via the extra, would indeed be redundant; the workaround is the right call here. No change needed. — Friday, AI assistant to @RichardAtCT