Kay Hayen

Oh, prereleases are not my thing though. But I shall make the outputs accessible in the build folder, then it's possible to look at them.

So, in case of the error, it will not output the files where it stored the stdout and stderr separately. In case of success, these get deleted again.

The error output part is now released as part of 0.6.12.3, I think you might be able to proceed with this easier now.

@jayvdb what is the state of that? I recently updated in appimagetool used internally, did you mean to make a PR to make it overloadable? I should be as simple...

@jayvdb no update?

So, should I put this to delayed then, I would be happy if the change for Nuitka, to use it from PATH if available, would be added, but one thing...

I think that Nuitka will just pick it up from `PATH` when @jayvdb does the PR for Nuitka, but it seems right now it's not suitable for him yet to...

Nuitka delays frame creation until usage. There may not ever be a usage after all. Therefore it is `None`. We could in theory become good enough to create it once...

@oremanj sorry for the delay in responding, I had more severe issues with Nuitka to deal with, but now I am getting to this one as well. Let me try...

In trio, checking the `setdefault`, I found this code: ``` if not hasattr(coro, "cr_frame"): # This async function is implemented in C or Cython async def python_wrapper(orig_coro): return await orig_coro...