This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: readline timeout too long for async gfx use
Type: performance Stage:
Components: Extension Modules Versions: Python 3.10, Python 3.9, Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: pmpp, twouters
Priority: normal Keywords:

Created on 2018-11-14 08:08 by pmpp, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg329891 - (view) Author: pmp-p (pmpp) * Date: 2018-11-14 08:08
unlike https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame which is fires about each 1/60 second : the callback for gui via PyOS_InputHook is as long as 0.1 second.

https://github.com/python/cpython/blob/8e0b05e2f4b9fd703cbe1ae8d058852ef3781f44/Modules/readline.c#L1192

using repl asyncronously with such a timer is a bad experience when using async opengl based gui : asyncio loop steps should be able to be served at vsync speed which is not actually possible because of hardcoded value.

0.008 seconds would not be so bad, best would be plan next call to hit T+ frametime ( with a default to 0.016 ) each pass inside the loop.

a use case for python would be panda3d and its various gui.

real life example in other mainstream language : the javascript repl in the browser console.
History
Date User Action Args
2022-04-11 14:59:08adminsetgithub: 79424
2020-09-14 23:11:05pmppsetversions: + Python 3.9, Python 3.10
2019-09-23 20:59:30pmppsetnosy: + pmpp
type: enhancement -> performance
2019-09-13 07:06:51pmppsetnosy: + twouters, - pmpp
2018-12-04 08:28:01pmppsetversions: + Python 3.8, - Python 3.7
2018-11-14 08:08:28pmppcreate