GeezerVison

This documentation feels a bit thin. Perhaps we could have examples of WSGI code using some of these aliases.

I agree about the examples, but when I procrastinated over two options, I gave up :)

1. Add an example to this section. But right below this section there is the "Example" section and this would feel like a duplication.
2. Add types to the example section. But in a way this distracts from the point of the example.

It might be good to add a note to the module docstring that any changes contributors want to make to this file will need to be made to typeshed simultaneously if they're to have any meaning to static type checkers

I'm not sure we should mention typeshed explicitly for a few reasons:

• I don't want to burden CPython contributors to need to contribute to typeshed.
• In typeshed we are pretty good in picking up changes, and for CPython we have quite some time to make these changes.
• While this is currently not the case, type checkers could in theory use the implementation module to type check instead of typeshed. In fact, I have an idea to optionally direct type checkers to the stdlib in cases like this, so it's possible that this comment would get outdated during the life time of Python 3.11.

This should probably be -> object. File objects typically return the number of bytes written as int.

Same for flush, although that doesn't typically return anything.

This is a bit embarrassing. :) Will fix.