| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
fixed indention to tabs
use Py_RETURN_NONE macro
added more error checks to on_completion_display_matches_hook
open question: Does PyList_SetItem(l, i, o) steal a reference to o in the case of an error?
|
|
|
|
| |
is a Python hook function. Fixes #1425.
|
|
|
|
| |
get_completion_type to readline.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
timeout on the select()
if an input hook has been defined. Patch by Richard Boulton.
This select() code is only executed with readline 2.1, or if
READLINE_CALLBACKS is defined.
Backport candidate for 2.5, 2.4, probably earlier versions too.
|
|
|
|
| |
Reported by Klocwork #152.
|
|
|
|
| |
Probably should be backported.
|
| |
|
|
|
|
|
|
|
|
|
| |
because (essentially) I didn't realise that PY_BEGIN/END_ALLOW_THREADS
actually expanded to nothing under a no-threads build, so if you somehow
NULLed out the threadstate (e.g. by calling PyThread_SaveThread) it would
stay NULLed when you return to Python. Argh!
Backport candidate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 1166660 ] The readline module can cause python to segfault
It seems to me that the code I'm rewriting here attempted to call any
user-supplied hook functions using the thread state of the thread that
called the hook-setting function, as opposed to that of the thread
that is currently executing. This doesn't work, in general.
Fix this by using the PyGILState API (It wouldn't be that hard to
define a dummy version of said API when #ifndef WITH_THREAD, would
it?).
Also, check the conversion to integer of the return value of a hook
function for errors (this problem was mentioned in the ipython bug
report linked to in the above bug).
|
| |
|
|
|
|
| |
this module any more.
|
|
|
|
| |
remove_history and replace_history. Will backport to 2.4.
|
|
|
|
|
| |
GNU readline exports a global variable that has such a name already
and the collision makes gcc4 doesn't compile the source.
|
|
|
|
|
|
| |
[ 1030629 ] PyOS_InputHook broken
with a couple of utterly inconsequential changes by me.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
module. Closes patch #675551. My apologies to Michal Vitecek for taking so
long to process this.
|
|
|
|
| |
[ 987287 ] Python 2.4a1, interpreter hanging on Keyboard Interrupt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 960406 ] unblock signals in threads
although the changes do not correspond exactly to any patch attached to
that report.
Non-main threads no longer have all signals masked.
A different interface to readline is used.
The handling of signals inside calls to PyOS_Readline is now rather
different.
These changes are all a bit scary! Review and cross-platform testing
much appreciated.
|
|
|
|
| |
readline module is loaded.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
PyOS_InputHook and PyOS_ReadlineFunctionPointer).
The inaccuracies were causing problems in framework builds on Mac OS X.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
METH_NOARGS functions are still called with two arguments, one NULL,
so put that back into the function definitions (I didn't know this
until recently).
Make get_history_length() METH_NOARGS.
|
|
|
|
|
|
| |
[ 676342 ] after using pdb readline does not work correctly
which is required to fix that bug. So maaybe a bugfix candidate.
|
|
|
|
| |
state swaps in readline).
|
| |
|
|
|
|
|
|
|
|
| |
- Whitespace normalization.
- Cleaned up some comments.
- Broke long lines.
|
|
|
|
|
|
|
|
|
| |
Check for readline 2.2 features. This should make it possible to
compile readline.c again with GNU readline versions 2.0 or 2.1; this
ability was removed in readline.c rev. 2.49. Apparently the older
versions are still in widespread deployment on older Solaris
installations. With an older readline, completion behavior is subtly
different (a space is always added).
|
| |
|
|
|
|
|
| |
This is evil. Only the user or the app's main() should do this!
We must save and restore the locale around the rl_initialize() call.
|
|
|
|
|
|
| |
for Py_Main().
Thanks to Kalle Svensson and Skip Montanaro for the patches.
|
| |
|
|
|
|
| |
also call using_history() to properly initialize history variables
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
readline in all python versions is configured
to append a 'space' character for a successful
completion. But for almost all python expressions
'space' is not wanted (see coding conventions PEP 8).
For example if you have a function 'longfunction'
and you type 'longf<TAB>' you get 'longfunction '
as a completion. note the unwanted space at the
end.
The patch fixes this behaviour by setting readline's
append_character to '\0' which means don't append
anything. This doesn't work with readline < 2.1
(AFAIK nowadays readline2.2 is in good use).
An alternative approach would be to make the
append_character
accessable from python so that modules like
the rlcompleter.py can set it to '\0'.
[Ed.: I think expecting readline >= 2.2 is fine. If a completer wants
another character they can append that to the keyword in the list.]
|
| |
|
| |
|
| |
|
|
|
|
| |
Clarify the docstring for get_history_length. Closes SF patch 494066.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modules/
_hotshot.c
dbmmodule.c
fcntlmodule.c
main.c
pwdmodule.c
readline.c
selectmodule.c
signalmodule.c
termios.c
timemodule.c
unicodedata.c
|