-
-
Notifications
You must be signed in to change notification settings - Fork 949
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
Remove Python 3.6 #1357
Remove Python 3.6 #1357
Conversation
Is that a visual bug on the pipeline? Python 3.6 is not running. |
Isn't it expected since you removed it in your branch? This check won't run in your PR. |
Ok... It makes sense... How do people merge PRs like this one, then? 🤔 |
As far as I remember the pipeline check won't be required, the approval will be enough. Might need double checking... |
Don't worry. I just open this for discussion initially. We'll see later. :) |
Only @tomchristie can merge this, as the pipeline will never pass. @tomchristie The reference about downloads per user is in the description of this PR, jfyk. |
I've updated the settings so that 3.7-3.10 are required. I don't have any strong feelings on this one. I suppose the sensible thing is mostly just that we update our packages consistently when we go for this. (Not for ay hard reasons, just because at least they're all on the same page then.) What is FastAPI's current version support? Do we have an outstanding PR for this change in uvicorn too? |
Link to those FastAPI stats... https://pypistats.org/packages/fastapi |
Let's wait some time before evaluating this again
I've talked to @tiangolo about this, and we reached the conclusion that we can wait some time before losing support for Python 3.6, so people can migrate to a new Python version. We can reevaluate the numbers some time from now. |
Yep! As @Kludex says, if possible, and if it's not being cumbersome to maintain, I would hold this for some time. 🙏 I assume there might already be "old" apps that can't migrate to 3.7 right away. If it gets annoying/cumbersome then yeah. But keeping support for 3.6 for a while might be appreciated by a few developers already stressed that their other libs don't support > 3.6 yet. 😅 |
|
Trio dropped support for Python 3.6. |
Not important on the dependency tree, but |
|
Daily downloads from PyPI Download Stats about Starlette:
3.18% of our users use Python 3.6. Ref.: https://pypistats.org/packages/starlette (date of the info above is 29 March 2022) Based on this, I'd like to go with this idea. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the thoughtful, data-driven approach to this update. 📈 👀 👍
I don't think maintaining Python 3.6 is a burden for Starlette (I have a different opinion on Uvicorn tho).
If we remove it on Uvicorn, should we also do it on Starlette?
This PR is to allow discussion having the changes that it implies in the same place. :)
Reference: https://pypistats.org/packages/starlette
Updated 14/01/22:
anyio
3.4.0 supports a feature to 3.7+.Updated 27/03/22:
setuptools
andjinja2
doesn't support Python 3.6 anymore.Note to future me: remove
jinja2
import conditional aboutcontext
function.