On 16/01/21 4:17 pm, Chris Angelico wrote:
But somewhere along the way, you're finding that there's a problem, which implies that SOMETHING is calling on C stdio. That thing, surely, should be the thing responsible for flushing?
The C library using stdio has no way of knowing that something else (e.g. Python) is bypassing stdio. That's an unusual thing to do in the C world, so you can't really blame the authors of the library for failing to anticipate it. It's also unreasonable to expect a C library to flush after every write, as that would defeat the purpose of stdio buffering. -- Greg -- https://mail.python.org/mailman/listinfo/python-list
