ipython / ipython/ipykernel

discuss multiple call to set_next_input

Abierto
#340 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
734
Forks
412
Merge medio
1 d 5 h
PR fusionados (30 d)
8

Descripción

See https://github.com/ipython/ipykernel/pull/323,

before big split, we were making sure each execution requests would not trigger multiple `set_next_input`, that was due to `?` triggering multiple `set_next_input` in a for loop and annoying some users.

I can see how calling multiple `set_next_input` could make sens, but I don't think the protection code should be in the kernel.

Guía de contribución

Abrir la guía de contribución

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.