On Tue, 2009-02-24 at 13:24 +0000, Ville M. Vainio wrote:
> On Tue, Feb 24, 2009 at 1:28 PM, Stephan Peijnik <email address hidden>
> wrote:
>
> > Without doing a check on this I expect that ipython, and not readline,
> > executes the python code entered. If that's the case it sure looks like
> > ipython causing the problem, and not readline.
>
> Try "%hist -r" to see what IPython thinks you actually typed.
Okay, looking at this makes me think it's readline again, thanks for the
hint.
On Tue, 2009-02-24 at 13:24 +0000, Ville M. Vainio wrote:
> On Tue, Feb 24, 2009 at 1:28 PM, Stephan Peijnik <email address hidden>
> wrote:
>
> > Without doing a check on this I expect that ipython, and not readline,
> > executes the python code entered. If that's the case it sure looks like
> > ipython causing the problem, and not readline.
>
> Try "%hist -r" to see what IPython thinks you actually typed.
Okay, looking at this makes me think it's readline again, thanks for the
hint.
--begin: %hist -r output--
1:
def a(b):
q=5
return q
2: q
3: %hist -r
--end: %hist -r output--
-- Stephan