[issue42044] Running Python in unbuffered mode may not write all contents to the console

Fabio Zadrozny added the comment: Seems fair. I just did a pull request to remove those limits. Please let me know if you think something else is needed there. -- ___ Python tracker

[issue42044] Running Python in unbuffered mode may not write all contents to the console

Change by Fabio Zadrozny : -- keywords: +patch pull_requests: +25264 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26678 ___ Python tracker ___

[issue42044] Running Python in unbuffered mode may not write all contents to the console

Eryk Sun added the comment: Text mode without a buffer isn't reliable. That said, Python 3.9 no longer supports Windows 7, so it can remove the 32 KiB limit on console I/O files. The size limit in Windows 7 and earlier is due to the LPC-based pseudo-files that it uses for I/O. Under the

[issue42044] Running Python in unbuffered mode may not write all contents to the console

New submission from Fabio Zadrozny : When running Python in unbuffered mode it may fail to write all the contents to the actual console (on Windows). The code below can reproduce the issue: ``` import sys s = '' for i in range(1,301): s += f"{str(i*100).zfill(10)}{'x' * 89}\n"