[REJECTED] PEP 605: A rolling feature release stream for CPython

Do I understand this correctly that the releases might end up being released for example like this?:

  • 3.9.0a1
  • 3.9.0b2
  • 3.9.0a3
  • 3.9.0a4
  • 3.9.0b5
  • 3.9.0b6
  • 3.9.0rc1

How does that technically work? It seems very unorthodox. As a Fedora Python maintainers we would need to hack around this a lot to make the versions sort properly. (However it’s fair to say that prerelases already need a certain level of hacks to make 3.9.0b5 < 3.9.0 work in RPM).

1 Like