Eric Brine

> I don't think private-use code points would be suitable, as these are valid Unicode Indeed. > where there are private-use code points that presumably map to characters in a...

One can work around this issue by adding the following to one's program: ```perl END { Inline::Python::py_finalize(); } ```

> That doesn't quite solve the output issue. See [here](https://stackoverflow.com/a/68671281/1830614); we get all the output, but it is scrambled. That's expected, completely normal, and not a bug in the module.

> > That's expected, completely normal, and not a bug in the module. > > Then it might warrant a comment in the docs. Would you take a PR for...

"running, each with its own process space", You mean address space? There isn't two. There's only process and thus only one address space. "Would this be an issue if we...

> The documentation state that we can redirect STDIN/STDOUT/STDERR to an already open handle. And you can. ```perl open( local *CHILD_OUT, ">", "outfile.txt" ) or die $!; my $pid =...

> > The documentation state that we can redirect STDIN/STDOUT/STDERR to an already open handle. > > And you can. > > ```perl > open( local *CHILD_OUT, ">", "outfile.txt" )...

The Lua 5.2 manual suggests `require` should return `true` when a module returns `nil`. > Once a loader is found, require calls the loader with two arguments: modname and an...

hmmm? It's pretty clearly stated in the previous message. Change > to >, and change > to >

Better test case: ``` $ perl -Mlib=lib,thirdParty/lib/perl5 -MData::UUID -e' my $x = "3\0" x 16; print Data::UUID->new->from_string($x), "\n"; print "done\n"; ' done ```