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

[Travis Griggs]

> On Oct 25, 2016, at 5:55 AM, Chris Angelico <rosuav at gmail.com> wrote:
> 
> On Tue, Oct 25, 2016 at 11:45 PM, Marko Rauhamaa <marko at pacujo.net> wrote:
>> Chris Angelico <rosuav at gmail.com>:
>> 
>>> On Tue, Oct 25, 2016 at 11:09 PM, Marko Rauhamaa <marko at pacujo.net> wrote:
>>>> Blocking calls are evil.
>>> 
>>> Oh, that's why. Got it. So because blocking calls are fundamentally
>>> evil, we have to... what? What's so bad about them? Remember, not
>>> every program is a server handling myriad clients.
>> 
>> Myriads or not, we are talking about interactive (or reactive) programs.
>> The paradigm of choice is event-driven programming.
> 
> Have you watched "Tron"? A program goes to the I/O tower to receive a
> message from the User. It's an active operation on the part of the
> program. The user cannot initiate it, only the program can.
> 
> Tron is extremely accurate in this way.

Thanks for this ChrisA. Rest of this thread has been meh for me, but this one post, definitely won my MostValueablePost for the thread. :)

Still chuckling.