In article <4ed6ffed$0$29986$c3e8da3$54964...@news.astraweb.com>, Steven D'Aprano <steve+comp.lang.pyt...@pearwood.info> wrote:
> Is there a way to disable readline support in the interactive interpreter > at runtime? Either from within an existing session, or when the session > starts up will do. I'm assuming Python uses the standard GNU readline(). If that's correct, then you can configure its behavior by editing your ~/.inputrc file. Try "man readline". I don't see any global "disable readline" flag, but you may be able to get that effect by deleting all the key mappings, or some such silliness. Another possibility is setting your TERM environment variable to something that readline can't support: ~$ TERM=asr33 ~$ python Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. Cannot read termcap database; using dumb terminal settings. Cannot read termcap database; using dumb terminal settings. Cannot read termcap database; using dumb terminal settings. >>> > If all else fails, are there any traps or pitfalls in installing a second > Python installation with readline support disabled? None at all, as long as you keep them from stomping on each other. The easiest method is probably to use virtualenv. BTW, readline is the coolest, awesomist, most frabjulously gnarly thing to be invented since the pointed stick. The idea that somebody would want to turn it off (even for testing) disturbs me deeply. -- http://mail.python.org/mailman/listinfo/python-list
