python / python/cpython

Split up the Changelog

Abierto
#137,795 2 comentarios 2 reacciones 1 asignado Ver en GitHub

@AA-Turner ya está trabajando en esto.

Desde el 15/8/2025.

docs
Lenguaje dominante
Python
Estrellas
77.2k
Forks
36k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

Documentation

Originally proposed in https://github.com/python/docs-community/issues/98

The full changelog is rather long, containing every NEWS entry since Python 3.5. We propose splitting it up into smaller individual files.

Doing this will also improve (parallel) builds -- build/NEWS (the file included by changelog.rst) is currently c. 55,000 lines long, the next longest file is 'only' 6,000 lines.

Consensus on the docs-community issue seemed to align with my proposal of splitting the changelog by minor version, meaning that we would have e.g. whatsnew/changelog/3.6.html.

I suggest that whatsnew/changelog/index.html would contain the entries for a pre-beta version (e.g. currently the 3.15 pre-alphas), but we could put these straight into whatsnew/changelog/3.15.html. Any strong opinions?

If we are happy to do this, I will propose the needed changes to blurb & then open PRs in CPython.

A

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.