Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

I was noticing that I wasn't getting any stdout/stderr output until the end of my batch job run from a built pex file. I'm assuming pex is using Popen.communicate or something similar somewhere in the call chain that holds on to the piped output.  Is this the expected behavior?

so, you built a PEX file, and then executed it, á la:
```./my.pex```
?

if so: PEX files don’t subprocess your code: they run using a bootstrap python, and then re-exec to whichever python matches your interpreter constraints

python _itself_ does do buffering though, and you might be encountering that? <https://stackoverflow.com/questions/107705/disable-output-buffering>

It's not clear if it makes a difference, but we actually are running it
python3 ./my.pex ...