e11bb77f31827f875b536c4dfed18343bcf8f458

When BPY_python_end() is not called, there can be buffered data still in `sys.stdout` or `sys.stderr`. This generally isn't an issue when those are connected to a terminal, but when they are read by another process (in the case of rendering with Flamenco, for example) we could miss the actual error message that's causing the exit in the first place. The following script demonstrates the issue; before this commit neither the writes to STDERR and STDOUT nor the traceback of the NameError were shown. #!/bin/bash cat > file-with-errors.py <<EOT import sys print('THIS IS STDERR', file=sys.stderr) print('THIS IS STDOUT', file=sys.stdout) nonexisting.monkey = 3 EOT blender --enable-autoexec -noaudio --background \ any-existing-blendfile.blend \ --python-exit-code 42 \ --python file-with-errors.py 2>&1 | cat Reviewers: campbellbarton, mont29 Reviewed By: campbellbarton, mont29 Subscribers: fsiddi Differential Revision: https://developer.blender.org/D4168
…
Description
No description provided
Languages
C++
78.1%
Python
15%
C
2.8%
GLSL
1.8%
CMake
1.2%
Other
0.9%