We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Originally posted by tomchristie September 19, 2024 Quoting from #2680...
I'm making some changes to the Starlette documentation to make it more modern and appealing. I intend to do the same with Uvicorn, and I intend to add a sponsors tab.
I'm making some changes to the Starlette documentation to make it more modern and appealing.
I intend to do the same with Uvicorn, and I intend to add a sponsors tab.
Yep, adding sponsors to the Starlette docs would be fantastic.
I'd suggest a unified approach across the encode docs? Perhaps let's take an agile approach and deal with this incrementally.
We could start with a unified approach for httpx, starlette, and uvicorn...
Perhaps we could start with...
The text was updated successfully, but these errors were encountered:
Agree, need some help?
Sorry, something went wrong.
No branches or pull requests
Discussed in #2695
Originally posted by tomchristie September 19, 2024
Quoting from #2680...
Yep, adding sponsors to the Starlette docs would be fantastic.
I'd suggest a unified approach across the encode docs?
Perhaps let's take an agile approach and deal with this incrementally.
We could start with a unified approach for httpx, starlette, and uvicorn...
Perhaps we could start with...
The text was updated successfully, but these errors were encountered: