Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Ipykernel releases and branches

Aberta
  • Algo errado?
#1,399 3 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
20/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
python
Domínio
release

Direção de pesquisa

Revise a sequência de branches proposta para main, 6.x, a branch anyio e o commit 7603443b, juntamente com as etapas de release para 6.30.0 e 7.0.0. Confirme primeiro a coordenação necessária com os maintainers e as proteções de branch do repositório; o trabalho estará concluído quando o layout das branches e os releases estiverem de acordo com o plano, sem interromper os pull requests existentes nem o version gating downstream.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

maintenance

(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:

  1. main renamed to anyio or some other name implying future or 8.x
  2. 6.x renamed to main
  3. 6.x before subshells were added (commit 7603443b) becomes the head of 6.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:

  1. Rename main to anyio, moving across all current PRs submitted against main
  2. Rename 6.x to main, set as default branch and update branch rules to protect against a push.
  3. Use commit 7603443b as the new head of 6.x
  4. Backport maintainance fixes from old main to new main and 6.x branches
  5. Release 6.30.0 from 6.x branch
  6. Release 7.0.0 from main branch
  7. Longer term discussion on the use of anyio vs tornado etc

I would like to start this soon, meaning weeks rather than months.

Linguagem predominante
Python
Estrelas
734
Forks
412
Merge médio
1d 9h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ipython/ipykernel

Todas as issues de ipython/ipykernel

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.