ipython / ipython/ipykernel

discuss multiple call to set_next_input

Open
#340 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
734
Forks
412
Avg merge
1d 5h
Merged PRs (30d)
8

Description

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.