Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Listen for key events in a CLI app

Parent

Listen for key events in a CLI app

+1
−2

I have a Python program like this:

done = False
while u and not done:
    i = u.pop()
    print(f"Processing {i}")
    do_big_task(i)

finish_up()

Since this takes a long time, the user might get tired of waiting. I want the program to also continually listen for a keystroke, such as space, and if the user presses this done will be set to True so that the loop will automatically stop at the next iteration.

Note that I still want finish_up() to run even if the loop is terminated early.

How can I do this?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

3 comment threads

Underresearched (2 comments)
Found on Stack Overflow (1 comment)
Fine-grained? (2 comments)
Post
+1
−0

First of all, the standard keystroke for interrupting a CLI program would be ctrl + C or whatever the windows equivalent is. Therefore, you will get the most consistent user experience if you use this standard keystroke for interrupting the program (rather than something custom like space).

One big advantage of using standard keystrokes, is that Python will raise a KeyboardInterrupt exception upon detection. As a result, we just have to write error handling code to stop the program properly.

A Minimal Working Example (MWE) of this code could look as follows:

import time

done = False
while not done:
    try:
        print("looping")
        time.sleep(1)
    except KeyboardInterrupt:
        done = True

print("done")

It might be even (slightly) better to wrap the entire code as follows:

import time

try:
    while True:
        print("looping")
        time.sleep(1)
except KeyboardInterrupt:  # not strictly necessary
    pass
finally:
    print("done")

Addendum: as indicated in the linked documentation (and mentioned in the comments), it would be important that the finish_up function has minimal runtime and allows to exit the program as quickly as possible. If the code in finish_up is lengthy, it might be useful/necessary to split up the code in a part that makes sure the program leaves a consistent state (if possible without too much overhead) and a (possibly slow) post-processing part that would appear inside of the try block. E.g.

import time

try:
    while True:
        print("looping")
        time.sleep(1)
    
    post_processing()
except KeyboardInterrupt:  # not strictly necessary
    pass
finally:
    print("finishing")
    clean_up()
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Questions (2 comments)
Questions
matthewsnyder‭ wrote over 1 year ago

While this makes sense, it seems a bit strange.

  1. Isn't it bad to use exceptions for flow control?
  2. Wouldn't this be surprising to a user who expects that Ctrl+C will terminate the program?
mr Tsjolder‭ wrote over 1 year ago
  1. that depends on what style of programming you wan't to use, but Python typically favours EAFP
  2. This is indeed an important detail that I forgot to mention (although it is indicated documentation I linked to): this assumes that the clean-up code effectively only does a minimal cleanup. I'll update the answer accordingly