@@ -59,14 +59,21 @@ This hackery is used on both Python 2 and Python 3 as neither version of
5959Python has native support for cmd.exe with unicode characters. There are
6060some limitations you need to be aware of:
6161
62- * this unicode support is limited to ``click.echo ``, ``click.prompt `` as
62+ * This unicode support is limited to ``click.echo ``, ``click.prompt `` as
6363 well as ``click.get_text_stream ``.
64- * depending on if unicode values or byte strings are passed the control
64+ * Depending on if unicode values or byte strings are passed the control
6565 flow goes completely different places internally which can have some
6666 odd artifacts if data partially ends up being buffered. Click
6767 attempts to protect against that by manually always flushing but if
6868 you are mixing and matching different string types to ``stdout `` or
6969 ``stderr `` you will need to manually flush.
70+ * The raw output stream is set to binary mode, which is a global
71+ operation on Windows, so ``print `` calls will be affected. Prefer
72+ ``click.echo `` over ``print ``.
73+ * On Windows 7 and below, there is a limitation where at most 64k
74+ characters can be written in one call in binary mode. In this
75+ situation, ``sys.stdout `` and ``sys.stderr `` are replaced with
76+ wrappers that work around the limitation.
7077
7178Another important thing to note is that the Windows console's default
7279fonts do not support a lot of characters which means that you are mostly
0 commit comments