I ran into a very strange behaviour of raw_input().
I hope somebody can tell me how to fix this.
(Or is this a problem in the python source?)
I will explain the problem by using 3 examples. (Sorry, long email)
The first two examples are behaving normal, the thirth is
strange...
I wrote the fo
TED]> wrote:
> On Jan 26, 7:23 am, Dox33 <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > I ran into a very strange behaviour of raw_input().
> > I hope somebody can tell me how to fix this.
> ===CUT===
> > *** Thirst, redirect stderr to file, STRANGE behaviour.
ther would have a correct working version.
On 27 jan, 04:20, Hrvoje Niksic <[EMAIL PROTECTED]> wrote:
> Dox33 <[EMAIL PROTECTED]> writes:
> > Thanks for your reply. Since I momentarily do not have the ability
> > to build a new python executable, I would like to ask for your
YES!
This is what I was looking for.
Great! All works fine now.
Thank you very much Gabriel.
Gabriel Genellina schreef:
> Add this on your sitecustomize.py module (or create one)
>
> import sys
> def raw_input(prompt=None):
>if prompt: sys.stdout.write(prompt)
>return original_raw_input()
