[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-28 Thread A.M. Kuchling
Changes by A.M. Kuchling : -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed versions: -Python 2.7, Python 3.3 ___ Python tracker ___

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-28 Thread Roundup Robot
Roundup Robot added the comment: New changeset 672614d809a1 by Andrew Kuchling in branch 'default': #1554133: Document PyOS_InputHook, PyOS_ReadlineFunctionPointer http://hg.python.org/cpython/rev/672614d809a1 -- nosy: +python-dev ___ Python tracker

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-24 Thread Terry J. Reedy
Terry J. Reedy added the comment: Can one of you three answer Kuchling's question about formatting a data entry that consists of a function pointer with function signature? -- nosy: +eric.araujo, ezio.melotti, georg.brandl ___ Python tracker

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-24 Thread A.M. Kuchling
A.M. Kuchling added the comment: One question about the patch: how to give the prototype expected for the function? I currently have it as: char *(*PyOS_ReadlineFunctionPointer)(FILE *stdin, FILE *stdout, char *prompt) Would it be better with a trivial function name, as in: char *func(FILE *

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-24 Thread Terry J. Reedy
Terry J. Reedy added the comment: I am not a C-api user, but the entries are pretty clear to me and seem ready to apply. The usage examples are a nice touch. OS Utilites is not where I would expect interpreter loop hooks, so I think the current location is better. -- stage: -> commit

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2013-05-24 Thread A.M. Kuchling
A.M. Kuchling added the comment: Here's a proposed patch to the c-api manual that describes these two pointers. I put them in the 'very high-level API' section. Maybe they belong in the Operating System Utilities section instead, but I think they're intertwined with the interpreter loop and t

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2011-03-08 Thread Terry J. Reedy
Terry J. Reedy added the comment: A.B, I believe you have looked at other areas of missing C-API docs. What do you think of this one? Is it still missing? -- nosy: +belopolsky, terry.reedy versions: +Python 3.3 ___ Python tracker

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2010-08-24 Thread Mark Lawrence
Changes by Mark Lawrence : -- assignee: -> d...@python nosy: +d...@python ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2010-08-07 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2010-07-09 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1554133] PyOS_InputHook() and related API funcs. not documented

2009-03-29 Thread Daniel Diniz
Daniel Diniz added the comment: The only mention I can find is in Misc/HISTORY: When the interpreter shell is invoked interactively, it attempts to import the readline module; when this fails, the default input mechanism is used. The hook variables are PyOS_InputHook and PyOS_Re