Ipykernel releases and branches
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
Línea de trabajo
Revisa la secuencia de ramas propuesta para main, 6.x, la rama anyio y el commit 7603443b, junto con los pasos de release para 6.30.0 y 7.0.0. Confirma primero la coordinación necesaria con los maintainers y las protecciones de ramas del repositorio; la tarea estará terminada cuando la estructura de ramas y los releases coincidan con el plan sin interrumpir los pull requests existentes ni el control de versiones de los proyectos posteriores.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
(Reposted from Jupyter Zulip)
There are some plans for ipykernel releases and branch manipulations that I am sharing here for maximum exposure. All comments gratefully received.
The latest ipykernel release was 6.29.5 in July 2024. The current main branch has almost but not quite complete implementations of anyio (instead of tornado) and subshells (JEP91) and it was originally intended that these would be in a 7.0.0 release. However, there are concerns about the use of anyio going forward so I have instead backported subshells to the current 6.x branch so it can be released without anyio (issue #1387).
The release of ipykernel with subshells but not anyio could have been 6.30.0 or 7.0.0, but we have decided that 7.0.0 is more sensible. Subshells do not have to be used and the implementation is backward compatible in the sense that it passes all downstream tests in the ipykernel CI but now shell channel messages are handled in a separate thread and this could break downstream projects that are assuming otherwise, or that might now receive messages with different timings or in a different order. 7.0.0 will allow downstream projects to version gate on ipykernel<7 while they check and fix such issues.
We also think it wise to make a 6.30.0 release anyway based on the 6.x branch before subshells was added so that we can support the 6.x branch whilst projects are transferring to 7.
This needs some branch manipulation in the ipykernel repo:
mainrenamed toanyioor some other name implyingfutureor8.x6.xrenamed tomain6.xbefore subshells were added (commit7603443b) becomes the head of6.x
I have sufficient permissions in the ipykernel repo to make these changes, but given the potential for messing things up I will only do in the presence of another maintainer; both Jason and Zach have previously said they might be available and are good choices being members of both the Jupyter Kernels Council and the EC.
Planned sequence of changes:
- Rename
maintoanyio, moving across all current PRs submitted againstmain - Rename
6.xtomain, set as default branch and update branch rules to protect against a push. - Use commit
7603443bas the new head of6.x - Backport maintainance fixes from old
mainto newmainand6.xbranches - Release 6.30.0 from
6.xbranch - Release 7.0.0 from
mainbranch - Longer term discussion on the use of
anyiovstornadoetc
I would like to start this soon, meaning weeks rather than months.
- Lenguaje dominante
- Python
- Estrellas
- 734
- Forks
- 411
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 9
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ipython/ipykernel
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 68/100
-
ipython/ipykernel#1550 · 1 comentario · 1 reacción · 1 asignado ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
Todos los issues de ipython/ipykernel
Issues similares
-
货币战争手改优先级配置缺少列表元素类型校验(P3) Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Abiertoarea: ci bug perceived difficulty: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ClickHouse/clickhouse-connect#1057 ·