Closing and not fixing is fair enough - I did not realize that this would be an issue that occurs in many places in stdlib.

I realize this is not a help forum, so I will ask elsewhere to see if there's some way to redirect all of sys.stderr in scenarios like these (running a service), because tracking down an issue like this takes a lot of time and finding the issue buried in a standard library caught me off guard.