You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?The text was updated successfully, but these errors were encountered: