[New-bugs-announce] [issue35243] readline timeout too long for async gfx use

pmpp report at bugs.python.org
Wed Nov 14 03:08:28 EST 2018


New submission from pmpp <pmpp.pub at gmail.com>:

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.

----------
components: Extension Modules
messages: 329891
nosy: pmpp
priority: normal
severity: normal
status: open
title: readline timeout too long for async gfx use
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35243>
_______________________________________


More information about the New-bugs-announce mailing list