We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using a simple cutie.select on Windows, a CPU core will be pegged to 80~90% while waiting for input due to readchar.
cutie.select
readchar
I tried switching to using this method with msvcrt.getch() and it seemed to use near 2% CPU usage while waiting for character input for comparison.
msvcrt.getch()
(In the screenshot the CPU has hyperthreading so even though 2 are pegged it's just a single core.)
Edit: I am going to open an issue on readchar, because it's a really easy fix of a while loop gone astray. magmax/python-readchar#42
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When using a simple
cutie.select
on Windows, a CPU core will be pegged to 80~90% while waiting for input due toreadchar
.I tried switching to using this method withmsvcrt.getch()
and it seemed to use near 2% CPU usage while waiting for character input for comparison.(In the screenshot the CPU has hyperthreading so even though 2 are pegged it's just a single core.)
Edit: I am going to open an issue on
readchar
, because it's a really easy fix of a while loop gone astray. magmax/python-readchar#42The text was updated successfully, but these errors were encountered: