RFC: Bump minimum supported Python version across AboutCode projects?

Aperta
  • Qualcosa non va?
#164 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

@DPR23 ci sta già lavorando.

Dal 4/11/2025.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
debian, fedora, linux, python, ubuntu
Ambito
ci-cd, documentation, release

Direzione di ricerca

Questo è un RFC, non una modifica al codice con ambito definito. Inizia leggendo la timeline di Python EOL collegata nell’issue e i README, changelog, file pyproject/setup e matrici delle versioni CI dei progetti interessati. Per considerarlo completato sarebbe necessaria una policy di supporto approvata da un maintainer prima di apportare qualsiasi aggiornamento alla documentazione, al packaging o alla CI.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

It would be good to have a simple plan to deprecate old Python versions and support new Python versions that would:

  • track the EOL timeline of Python proper https://devguide.python.org/versions/
  • but also track support of Python version in mainline Linux distros. See below.
  • and also consider the context of a given project (library vs. application). Libraries may need a wider support of versions, while apps can have narrower ranges.
  • and also consider which versions in which packaging are getting major bug and security fixes.

What this mean is that the Python.org EOL'ed versions may still need to supported.

Alternatively if we start promoting only containerized deployments, we could more readily deprecated and drop older Python versions, including non EOL'ed versions, but to the detriment of using the code a libraries....

We should also consider the many small things related to change of supported versions:

  • CHANGELOG entries, READMEs and documentation updates
  • pyproject/setup changes to add version constraints?
  • Ci test suites across versions

One approach would be to have two policies:

  • for libraries, we could support all Python versions that are receiving security and bug fixes, as of today, 3.9 to 3.12
  • for apps, we could support only container deployments with a more restricted number of more recent versions, like the latest stable only 3.12
  • for new versions we should define when we adopt them as supported. For instance 3.13 has just been released, and we could state that we work to support a new major release (like 3.13) within 12 months of its publication. Or we could also support re-releases, but frankly this is not something I look forward to.

As for supported versions, here is the https://devguide.python.org/versions/ EOL timeline:
Screenshot 2024-12-07 at 11-20-29 Status of Python versions

And here is the distro support for various versions:

  • On Debian:

Package python3

buster (oldoldstable) (python): interactive high-level object-oriented language (default python3 version)
3.7.3-1: amd64 arm64 armhf i386
bullseye (oldstable) (python): interactive high-level object-oriented language (default python3 version)
3.9.2-3: amd64 arm64 armel armhf i386 mips64el mipsel ppc64el s390x
bookworm (stable) (python): interactive high-level object-oriented language (default python3 version)
3.11.2-1+b1: amd64 arm64 armel armhf i386 mips64el mipsel ppc64el s390x
trixie (testing) (python): interactive high-level object-oriented language (default python3 version)
3.12.6-1: amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 s390x
  • On Ubuntu:

Package python3

focal (20.04LTS) (python): interactive high-level object-oriented language (default python3 version)
3.8.2-0ubuntu2: amd64 arm64 armhf i386 ppc64el riscv64 s390x
jammy (22.04LTS) (python): interactive high-level object-oriented language (default python3 version)
3.10.6-1~22.04 [security]: amd64 i386
3.10.4-0ubuntu2 [ports]: arm64 armhf ppc64el riscv64 s390x
jammy-updates (python): interactive high-level object-oriented language (default python3 version)
3.10.6-1~22.04.1: amd64 arm64 armhf i386 ppc64el riscv64 s390x
noble (24.04LTS) (python): interactive high-level object-oriented language (default python3 version)
3.12.3-0ubuntu1: amd64 arm64 armhf i386 ppc64el riscv64 s390x
  • On Fedora

Fedora 34 3.9.2-1.fc34
Fedora 36 3.10.11-1.fc36
Fedora 38 3.11.9-2.fc38
Fedora 40 3.12.7-1.fc40
Fedora 41 3.13.0-1.fc41

Lingua principale
Batchfile
Stelle
310
Fork
255
Merge medio
10h 5m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aboutcode-org/aboutcode

Tutte le issue di aboutcode-org/aboutcode

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.