Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New output redirection in ipykernel 6.0 clutters notebooks #737

Closed
jpanetta opened this issue Aug 11, 2021 · 2 comments · Fixed by #752
Closed

New output redirection in ipykernel 6.0 clutters notebooks #737

jpanetta opened this issue Aug 11, 2021 · 2 comments · Fixed by #752

Comments

@jpanetta
Copy link

I am finding the new functionality that captures all output written to stdout/stderr for display in notebooks disruptive. I develop C++ modules that manually redirect select output to the Python output streams while letting more verbose log messages go to the terminal where they won't clutter the notebook; there are existing libraries to support this use case. Unfortunately, all output is now dumped indiscriminately into the notebook. It would be great to still be able to take advantage of the two distinct output streams.

Is it possible to add a configuration option to disable this new behavior/expose the new watchfd argument to the user? Or is there a way to configure my modules to bypass the capture mechanism and go quietly into the terminal?

@ccw630
Copy link

ccw630 commented Aug 18, 2021

Face the same situation and what's more can lead to receive useless logs especially when using pyspark.

@jpanetta
Copy link
Author

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants