Repository navigation
Python's STDOUT isn't flushed #32
Description
As reported on StackOverflow, Python's STDOUT isn't flushed
use feature qw( say );
use Inline Python => <<'END_OF_PYTHON_CODE';
def test_print() -> int:
print("In the python test print")
return 32
END_OF_PYTHON_CODE
say "Got back ", test_print();Output:
$ perl a.pl
In the python test print
Got back 32
$ perl a.pl | cat
Got back 32
Who knows what other destruction doesn't occur.
Activity
ikegami commentedon Aug 5, 2021
One can work around this issue by adding the following to one's program:
END { Inline::Python::py_finalize(); }matthewpersico commentedon Aug 5, 2021
That doesn't quite solve the output issue. See here; we get all the output, but it is scrambled.
ikegami commentedon Aug 5, 2021
That's expected, completely normal, and not a bug in the module.
matthewpersico commentedon Aug 16, 2021
Then it might warrant a comment in the docs. Would you take a PR for such?
ikegami commentedon Aug 17, 2021
Whenever you have two things trying to use one resource (e.g. a terminal), coordination (e.g. synchronization) is required, or at least needs to be considered.
matthewpersico commentedon Aug 18, 2021
Yes, I see now. Here, we have two interpreters running, each with its own process space. Would this be an issue if we were inlining a compiled language? I would think not because then the inline'd code is just a library being executed in the Perl process space.
The distinction is important to me in terms of how I want to propose a documentation PR - I propose it would go in the Inline docs themselves under a heading like "Considering Non-Compiled Inline Modules"
niner commentedon Aug 18, 2021
ikegami commentedon Aug 18, 2021