Why doesn't Python include non-blocking keyboard input function?

[Terry Reedy]

On 10/27/2016 1:49 AM, Marko Rauhamaa wrote:
> Terry Reedy <tjreedy at udel.edu>:
>
>> On 10/26/2016 8:33 AM, Marko Rauhamaa wrote:
>>> Maybe there should be some way to get the raw events from the PTY.
>>
>> PTY?  Must be Linux-specific.  Most beginners are not on Linux.
>
> A PTY is an emulated console (<URL:
> https://en.wikipedia.org/wiki/Pseudoterminal>). I don't know Windows but
> I would guess cmd.exe does something similar there.
>
> Also, I have no statistics on most beginning programmers operating
> systems.
>
>>> But what would be wrong in a GUI PTY API? No windowing,
>>
>> 'No windowing'? Python normally runs in a text widget in a window,
>> programmed to emulate a dumb terminal.
>
> Must be Windows-specific.

Not as I meant the above.

When I used unix in the 1980s, the full screen ran csh until one started 
another full screen application.  MSDOS was the same. Every contemporary 
photo of modern Linux or Mac I have seen has a desktop with windows just 
like Windows.  Do people on Linux still commonly use full-screen, no 
window text editors like the one I had?  On Windows, there are full 
screen games, but I have never seen a full-screen, no-window text 
application.

Since modern screen are pixel graphics screens, rather than character 
screens, there must be a widget, whether standard with the OS or custom 
to the console, that emulates the old fixed-pitch character screens.  At 
least on Windows, C Programs that run with the console still get 
characters entered by users and send characters to be displayed.

-- 
Terry Jan Reedy