hypercorn VS python-gunicorn-uvicorn

In addition [Hypercorn](https://github.com/pgjones/hypercorn) (a ASGI and WSGI) also does not use gunicorn, having migrated many years ago.

You might find some recommendations to use hypercorn rather than uvicorn, I tried that initially but I couldn't resolve an issue with socket permission, I raised it as a bug in their GitHub repo.

for those wishing to use http3 with a Python web framework, the ASGI hypercorn[1] currently supports it.

made a Django example last week with a sample client based on the examples from aioquic[2]: https://github.com/djstein/django-http3-example

this example also includes the first pass at async Django REST Framework using adrift[3] based on these GitHub issues:

- https://github.com/encode/django-rest-framework/pull/8617

- https://github.com/encode/django-rest-framework/issues/8496

sources

[1]: https://github.com/pgjones/hypercorn

[2]: https://github.com/aiortc/aioquic

[2]: https://github.com/em1208/adrf

what about hyopercorn ? looks like it supports http3

By using Hypercorn like so:

As a note there is also a gunicorn uvicorn image, but in general you're better of just using uvicorn and launching multiple images rather than having gunicorn and uvicorn in one container.

The multi-py project has a cross platform gunicorn container that works with Intel and Arm out of the box.

https://github.com/multi-py/python-gunicorn

There's also a uvicorn one there for people who want the async features.

https://github.com/multi-py/python-uvicorn

And a container that combines both (although it's often better to just use uvicorn and add more containers to your API to scale up).

https://github.com/multi-py/python-gunicorn-uvicorn