diff options
| author | Eric Eastwood <erice@element.io> | 2025-05-13 10:40:49 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-13 10:40:49 -0500 |
| commit | a3bbd7eeabee7c6b229e95e0e04af5b430ea32db (patch) | |
| tree | 5be44c19433439b07300bfbb8ee0eba9ec4452d3 /docs/usage/configuration/config_documentation.md | |
| parent | Fix a couple type annotations in the `RootConfig`/`Config` (#18409) (diff) | |
| download | synapse-a3bbd7eeabee7c6b229e95e0e04af5b430ea32db.tar.xz | |
Explain why we `flush_buffer()` for Python `print(...)` output (#18420)
Spawning from using this code elsewhere and not knowing why it's there. Based on this article and @reivilibre's experience mentioning `PYTHONUNBUFFERED=1`, > #### programming languages where the default “print” statement buffers > > Also, here are a few programming language where the default print statement will buffer output when writing to a pipe, and some ways to disable buffering if you want: > > - Python (disable with `python -u`, or `PYTHONUNBUFFERED=1`, or `sys.stdout.reconfigure(line_buffering=False)`, or `print(x, flush=True)`) > > _-- https://jvns.ca/blog/2024/11/29/why-pipes-get-stuck-buffering/#programming-languages-where-the-default-print-statement-buffers_
Diffstat (limited to 'docs/usage/configuration/config_documentation.md')
0 files changed, 0 insertions, 0 deletions