You'd need to start with fixing it in blessings. But with WSL, isn't fcntl usage an issue of the past?

it is, but its a pain to run a virtual machine (because it is in the end of day) each time I wanna work with python, specially working with some python native toolkits e.g. working with hooks or any other windows native thing

I'll give a look to blessing, but I guess, that means I have no luck

Instead of fixing Blessings, that seems unmaintained... Why not switch to blessed, that is maintained, and has Windows support?

@thomasballinger Would switching to blessed by an option for curtsies?

curtsies would also need to use functions other than from termios on Windows for it to actually work there.

The colorconsole project can serve as a reference on providing similar functionality to termios on Windows.

Textual's "console drivers" also could be used as a reference.

Edit: or just use what Blessed (and Jinxed) provide, I guess :-)

hmm, I guess with this new info I have to give a try to read blessed doc and bpython source, I prefer this issue be opened for a time. because it seems like there is an act to be done here

Edit: I saw @sebastinas made a move to blessed (3 days ago) in curtsies lib, so I wish bpython be fixed for windows asap

There are still some open issues in curtsies. Most of those can probably be fixed by re-using more of blessed's functionalities.