Windows support

[thomasballinger]

I don't know how possible this is: the main issues in my mind are:

• nonblocking reads of stdin
• translating ANSI escape sequences to window (colorama does most of this)
• finding out the current cursor position
• signal handling is different - curtsies needs to be able to be responsible for its own signal handling

@lohmataja and I were thinking about how possible it was. Nonblocking reads could be handled by a thread, ANSI escape sequence translation can happen with colorama mostly. We could move most signal handling back into curtsies, and pass in callbacks that could be triggered by a signal handler or whatever Windows does.

The first step might be getting fmtstr compatible (mostly just colorama), then getting formatstring.dumb_display working, then getting window.FullscreenWindow working. Next would be working on input.Input.

[thomasballinger]

Look at what the python prompt toolkit team did at https://github.com/jonathanslenders/python-prompt-toolkit/tree/38ea451dc4d8e13937a4ccad680d02815fd9febc/prompt_toolkit/eventloop for a take on this

[thomasballinger]

The goal of this would be to get bpython running on Windows - any hacks requires to make this happen would be acceptable. Blessed is trying to do this right, see jquast/blessed#18

[coolcoder613eb]

on windows 10/11 ansi escapes work,
you just have to do os.system('') and it works.