You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bpo-1744456: Expose non-blocking callbackAPI in readline module
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2010-07-10.10:26:25.297>created_at=<Date2007-05-06.18:07:07.000>labels= ['type-feature', 'library']
title='Expose callback API in readline module'updated_at=<Date2010-07-10.10:26:25.291>user='https://bugs.python.org/strank'
I think it still needs some work if you want to make it impossible for
users of the API to wreck the interactive prompt. If this possibility is
considered ok (it does not make sense to use the callback api from the
interactive prompt anyway), I think it's ok.
But someone with more readline experience should probably look at it... :-)
BreamoreBoy commented on Jul 10, 2010
BreamoreBoymannequin
Mannequin
More actions
Can this be closed as a duplicate as bpo-1744456 has a patch?
Activity
strank commentedon May 6, 2007
This is a request to expose the
callback API_ of GNU readline in the readline module in the Python library... _callback API: http://cnswww.cns.cwru.edu/php/chet/readline/readline.html#SEC41
This interface is suitable for asynchronous use, such as with twisted.
It is possible to expose the functions on Unix with ctypes::
but it would be much better to expose them "officially".
tiran commentedon Jan 6, 2008
A patch is always welcome
strank commentedon Jan 7, 2008
I am pretty sure I posted a patch in the sf patch tracker... oh yes,
here it is: http://bugs.python.org/issue1744456
I think it still needs some work if you want to make it impossible for
users of the API to wreck the interactive prompt. If this possibility is
considered ok (it does not make sense to use the callback api from the
interactive prompt anyway), I think it's ok.
But someone with more readline experience should probably look at it... :-)
BreamoreBoy commentedon Jul 10, 2010
Can this be closed as a duplicate as bpo-1744456 has a patch?
birkenfeld commentedon Jul 10, 2010
Yes, that makes sense (the two issues come from the SourceForge era, where bugs and patches had different trackers).