Skip to content
New issue

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

✨ Add support for Python 3.12 #191

Closed

Conversation

shepilov-vladislav
Copy link

No description provided.

@shepilov-vladislav
Copy link
Author

@tiangolo can it be merged?

@shepilov-vladislav
Copy link
Author

@tiangolo Maybe you should give maintainer rights additionally to some other active user of the community? Python 3.12 is released in October 2023 and moreover, your framework supports it. I suspect you have a lot of work to do and don't have time to review all the pull requests. But we depend on your code, and we maintain our codebase on the current version of Python. And there is only one way out in this situation - to keep additional versions of docker images in your docker registry until you merge them.

@eliasdjup
Copy link

+1

2 similar comments
@theobouwman
Copy link

+1

@mhkarimi1383
Copy link

+1

@mhkarimi1383
Copy link

@tiangolo We could switch to a templating structure and getting last N versions of python, so no need to have update like this anymore :)

@tiangolo
Copy link
Owner

Thanks for the interest! 🍰

Now that Uvicorn supports managing workers with --workers, including restarting dead ones, there's no need for Gunicorn. That also means that it's much simpler to build a Docker image from scratch now, I updated the docs to explain it.

Because of that, I deprecated this Docker image: https://github.com/tiangolo/uvicorn-gunicorn-docker#-warning-you-probably-dont-need-this-docker-image

Given that, I'll now close this one, but thanks for the effort! ☕

@tiangolo tiangolo closed this Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants