Add gaurds to redirect C++'s stdout/stderr streams to python's stdout/stderr streams #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
C++'s stdout/stderr and Python's stdout/stderr streams are two different streams.. normally this is not a problem but colab ignores C++'s streams. To make colab see C++'s streams they need to be redirected to Python's streams
if the statement
py::call_guard<py::scoped_ostream_redirect, py::scoped_estream_redirect>()is added to a function's definition then its stdout/stderr gets redirected. I do that for the decoding methods for simplex and tesseract.so statements like this with
verbose=Truewill have their stdout redirectedI also added a context manager that can be used to do this from inside python