[2025] Releasing version 3.0.0

[amotl]

About

We are intending to release Responder 3.0.0.

Notes

• responder 3.0.0 is largely compatible with responder 2.0.0,
  and unlocks using it with Python 3.11 and higher.
• All subsystems have been refactored to be true extensions,
  see responder.ext.{cli,graphql,openapi,schema}.

Preview

Pre-release packages are available on PyPI. Feedback is very much welcome.

• PyPI: responder==3.0.0.dev0
• Documentation: https://responder.readthedocs.io/
• Installation:

  uv pip install --upgrade 'responder>=3.0.0.dev0'
  

Demo

Demonstrate package downloading and invocation works well.

uvx --with='responder[cli]>=3.0.0.dev0' responder --version

variants

uv solo

uv run --with='responder[cli]>=3.0.0.dev0' -- responder --version
uv run --python=3.8 --with='responder[cli]>=3.0.0.dev0' -- sh -c "python -V; responder --version"
uv run --python=3.13 --with='responder[cli]>=3.0.0.dev0' -- sh -c "python -V; responder --version"

uv+Docker

export PYTHON=python3.8
export PYTHON=python3.13
docker run "ghcr.io/astral-sh/uv:${PYTHON}-bookworm-slim" \
  uv run --with='responder[cli]>=3.0.0.dev0' -- responder --version

Downstream

Updates to responder 3.0.0, validated on downstream projects.

• Update to responder 3.0.0.dev0, and support Python 3.13 daq-tools/vasuki#28

Details

What's inside

Maintenance

Currently, the package can't be installed on current systems, i.e. Python 3.11+.
The next release intends to improve this situation.

• Uvicorn version too old ? #470
• Vulnerability in referenced starlette version #496
• Can't install on Debian bookworm with Python >= 3.11 #518
• New release pending? / Python >= 3.11 need a compiler when installing #522
• Maintenance 2024-10 #525

Code wrangling

Some subsystem modules got lost on the main branch.
Those patches bring them back into responder.ext.

• Feature: Bring back CLI interface #547
  • CLI 2024: Re-add command line interface #549
  • CLI 2025: Use pueblo.sfa for responder run #576
• Feature: Bring back GraphQL extension #551
  • GraphQL: Re-add extension and dependencies (2024) #554
• Feature: Bring back OpenAPI extension
  • OpenAPI: Refactor module to responder.ext.openapi #555

Documentation

The documentation is on RTD now.

• Using Read the Docs #564
  • https://responder.readthedocs.io/

[adrian-kuhn]

Hi Andreas,
that's good news! I'm happy to test it with our next release and let you now, if we encounter any problems.

Thank you for your great work with this great library,
Adrian

[amotl]

Hi again. I am hereby pinging all 77 contributors to possibly check out the new pre-release, probing the chance that they might still be using the package in one way or another.

http "https://api.github.com/repos/kennethreitz/responder/contributors?per_page=100" | \
  jq -r '["@" + .[].login] | sort | @csv' | tr -d '"' | sed 's/,/, /g'

/cc @0x49D1, @0xflotus, @BNMetrics, @CianciuStyles, @EdwardBetts, @FirstKlaas, @Hwesta, @JayjeetAtGithub, @MRSharff, @MerleLiuKun, @MichaelPereira, @Nitish18, @ParthS007, @StevenAvelino24, @TomFaulkner, @aaqaishtyaq, @aitoehigie, @amikrop, @artemgordinskiy, @barrust, @carlodri, @cdfuller, @condemil, @daikeren, @daphil19, @ewjoachim, @frostming, @gdamjan, @goodbadwolf, @ibnesayeed, @javad94, @jeremiahpslewis, @jonbeebe, @jordaneremieff, @josegonzalez, @kennethreitz, @kobayashi, @majiang, @mathiasose, @metakermit, @mlschneid, @mmanhertz, @mtcronin99, @nicksspirit, @nicoddemus, @parberge, @pbsds, @pesap

[amotl]

Splitted into a second post, because GitHub apparently has a limit on the maximum number of referenced user handles.

/cc @pyasi, @rcatajar, @repodevs, @rparrapy, @rpost, @ryuuji, @serhii73, @sheb, @shyamjos, @sloria, @squiddy, @steinnes, @tabotkevin, @taoufik07, @tedder, @timgates42, @timofurrer, @tkamenoko, @tomchristie, @tselepakis, @ucpr, @valtyr, @vbarbaresi, @vlcinsky, @vuonghv, @waghanza, @xyb

[waghanza]

responder has been removed from https://web-frameworks-benchmark.netlify.app/result?l=python, since the-benchmarker/web-frameworks#5769 (comment)

I can re-introduce it if you like ❤

[waghanza]

can you give me a simple code that implements 3 endpoints : GET /, POST /user/ and GET /user/:id ? and obviously make me a recommendation for engine to use in a production environment (uvicorn, gunicorn, daphne, hypercorn ...) @amotl ?

[amotl]

Hi @waghanza, we are just leaving for a week of vacation, so I am sorry I can't provide any more details right now. Responder uses uvicorn, if that answers your second question? Maybe @kennethreitz can help out?

[waghanza]

I can not install this beta. I have

pip install .root@8d1c5695aad9:/usr/src/app# pip install .
Processing /usr/src/app
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [14 lines of output]
      Traceback (most recent call last):
        File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
          ~~~~^^
        File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
        File "/usr/local/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-wu2i3oks/overlay/lib/python3.13/site-packages/flit_core/buildapi.py", line 31, in get_requires_for_build_wheel
          module = Module(info.module, Path.cwd())
        File "/tmp/pip-build-env-wu2i3oks/overlay/lib/python3.13/site-packages/flit_core/common.py", line 59, in __init__
          raise ValueError("No file/folder found for module {}".format(name))
      ValueError: No file/folder found for module server
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.

[notice] A new release of pip is available: 24.3.1 -> 25.0
[notice] To update, run: pip install --upgrade pip
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

my pyproject is

[build-system]
build-backend = "flit_core.buildapi"
requires = ["flit_core"]

[project]
name='server'
version = '1.0.0'
description = "Simple benchmark implementation"
dependencies = ["responder==3.0.0.dev0"]