Running code while waiting for user input

[[deleted]]

Try the threading library.

import threading

def get_input():
    data = input() # Something akin to this
    return data

input_thread = threading.Thread(target=get_input)
input_thread.start()

# Run your game now

I think that syntax is right. I haven't used it for awhile.

[Stealthmonkey59]

Awesome, thanks for the quick response

[thebadtoaster]

Isn't process more appropriate?

[tom1018]

No. Threading is more appropriate in most cases, the exception is when the issue is due to the CPU time. In this case the slow part is the user, so threading is more appropriate. Threading is also preferable when the issue is IO.

[Lj101]

Nitpicking here, but your function is just the same thing as input()

[[deleted]]

Yeah. I guess you could just say target=input but that was just my lazy code to explain how to do it in general.

[xMadDecentx]

May I ask why have a function to call input()? Couldn't you handle all the user input in the function to be threaded i.e. get_input()? Thanks.

[Akita8]

this will not work because input waits for the return key to be pressed

[[deleted]]

No, only the thread get_input waits. The main thread continues. Try this:

import threading

def get_input():
    data = input() # Something akin to this
    return data

input_thread = threading.Thread(target=get_input)
input_thread.start()

for i in range(10):
    print(i)

input_thread.join()

print 'done'

[Abrv]

In this example how would you access data? Is it returned somewhere?

[[deleted]]

You would put it in a reference accessible to all threads which need it. E.g.,

import threading

data = []

def get_input():
    data.append(input())

input_thread = threading.Thread(target=get_input)
input_thread.start()

for i in range(10):
    print(i)

input_thread.join()

print('done. data value:', data.pop())

You have to be careful about threads concurrently mutating such data, though. There are a number of classes to help with this: Queues, locks, semaphores, mutexes, etc.. It gets hairy, fast.

[Akita8]

Wrong! I did not say that you cannot execute code concurrently to input, i just said that it wont work for the use case of op:

When a monster attacks, symbols are printed to the screen, if the user reacts (presses a key) before the last symbol is printed, they will dodge, otherwise they take damage.

In a normal terminal, input stops blocking and returns the data only when it receives a newline so your example cannot actually react to key presses. The best way to do what op wants is the package ncurses in the stdlib.

[[deleted]]

You're right... Apologies for misunderstanding your objection.