This check was added for bpo-11395 in 2011. Versions of Windows before
Windows 8 required the check as write size to a tty was limited (
python#55604 (comment)).

Based on PEP 11, the last Windows 8 support ended in 2023, so this is no
longer needed on any currently supported windows platforms.

That large writes to console succeed is tested by
test_os.test_write_windows_console, which passes in my testing on
Windows 11.

It's possible there are still objects on windows which error on a write
too large, this leaves in place some code to handle (ex. Pipes and
ENOSPC). Write can also still be interrupted and resumed (EAGAIN, etc).

If there are other Windows objects or platform files which limit write
size, callers should wrap the `os.write` function.

This check was added for bpo-11395 in 2011. Versions of Windows before
Windows 8 required the check as write size to a tty was limited (
python#55604 (comment)).

Based on PEP 11, the last Windows 8 support ended in 2023, so this is no
longer needed on any currently supported windows platforms.

That large writes to console succeed is tested by
test_os.test_write_windows_console, which passes in my testing on
Windows 11.

It's possible there are still objects on windows which error on a write
too large, this leaves in place some code to handle (ex. Pipes and
ENOSPC). Write can also still be interrupted and resumed (EAGAIN, etc).

If there are other Windows objects or platform files which limit write
size, callers should wrap the `os.write` function.

This check was added for bpo-11395 in 2011. Versions of Windows before
Windows 8 required the check as write size to a tty was limited (
python#55604 (comment)).

Based on PEP 11, the last Windows 8 support ended in 2023, so this is no
longer needed on any currently supported windows platforms.

That large writes to console succeed is tested by
test_os.test_write_windows_console, which passes in my testing on
Windows 11.

It's possible there are still objects on windows which error on a write
too large, this leaves in place some code to handle (ex. Pipes and
ENOSPC). Write can also still be interrupted and resumed (EAGAIN, etc).

If there are other Windows objects or platform files which limit write
size, callers should wrap the `os.write` function.

This check was added for bpo-11395 in 2011. Versions of Windows before
Windows 8 required the check as write size to a tty was limited
(python#55604 (comment)).

Based on PEP 11, the last Windows 8 support ended in 2023, so this is no
longer needed on any currently supported windows platforms.

That large writes to console succeed is tested by
test_os.test_write_windows_console, which passes in my testing on
Windows 11.

It's possible there are still objects on windows which error on a write
too large, this leaves in place some code to handle (ex. Pipes and
ENOSPC). Write can also still be interrupted and resumed (EAGAIN, etc).

If there are other Windows objects or platform files which limit write
size, callers should wrap the `os.write` function.

 - Unify capping code to always respect character
   boundaries.
 - Make a soft cap rather than a hard limit
 - Make the cap for what _should_ be
   non-interactive / filesystem files 5 times that
   of interactive files (so big writes are faster)
 - Make write size for expected intractive to be
   1 MB (1024 * 1024), feels relatively responsive
   on my machines.