Is that a visual bug on the pipeline? Python 3.6 is not running.

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.
I guess it's the same when you add a new Matrix, in that PR the new matrix won't be required since the changes aren't in master.

Ok... It makes sense... How do people merge PRs like this one, then? 🤔

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...

Ok... It makes sense... How do people merge PRs like this one, then? thinking

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?

Sorry to jump in here, I don't know about FastAPI's plans for python 3.6 but this pypistats might be worth considering:

Update: I'm not sure how accurate the numbers are but ignoring the recent peaks, there a few thousand downloads of Python3.6 happening every day.

Link to those FastAPI stats... https://pypistats.org/packages/fastapi

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. 😅

anyio 4.0 will drop Python 3.6, jfyk.

Trio dropped support for Python 3.6.

Not important on the dependency tree, but coverage dropped support as well.

pytest dropped support as well.

Daily downloads from PyPI Download Stats about Starlette:

3.8: ~95k
3.7: ~78k
3.9: ~44k
3.10: ~16k
3.6: ~10k

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.