On Fri., 29 Nov. 2019, 6:15 am Facundo Batista, <facundobatista@gmail.com> wrote:

El jue., 28 de nov. de 2019 a la(s) 12:35, Facundo Batista
(facundobatista@gmail.com) escribió:

> Did we take a decision of what comes after 3.9?
>
> Do we have a PEP for that decision? (couldn't find it)

Thanks everybody for the responses.

So 3.10 it is, not a hard made decision, but the collective trend.

Should we have a PEP for this?

We will at least have the 3.10 release schedule PEP, and the accepted release cadence change PEP uses 3.10 in its examples, but it's probably a good idea to have a short "Handle double-digit minor release numbers" PEP that explicitly summarises the compatibility issues that are likely to arise.

https://www.python.org/dev/peps/pep-0598/#why-not-switch-directly-to-full-semantic-versioning touched on the topic during the release cadence change discussion, but the final set of PEPs for that (602, 605, 607) all took it for granted that we'd be publishing 3.10 after 3.9.

Cheers,

Nick.

P.S. In addition to the flake8 plugin, Anthony Sottile also published

https://github.com/asottile/python3.10 to help with checking compatibility in advance.