ipykernel unconditionally calls `sys.stdout.flush()`

Open
#1,119 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
jupyter, python
Domain
backend

Research direction

Search the ipykernel source for the unconditional sys.stdout.flush() and sys.stderr.flush() calls described in the issue. Confirm the affected paths tolerate None streams, guard each flush accordingly, and run the relevant test suite to verify kernel behavior when either stream is unavailable.

Written by the indexing model from the issue text.

Description

ipykernel unconditionally calls sys.stdout.flush() and sys.stderr.flush(). This is a problem when either sys.stdout or sys.stderr is None, such as in pythonw.exe on windows, or Pyinstaller's windowed mode. All of these checks should be garded with a not-None check.

Dominant language
Python
Stars
734
Forks
411
Avg merge
1d 2h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ipython/ipykernel

All issues in ipython/ipykernel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.