Reporting Python bugs (was: Can someone explain this unexpected raw_input behavior?)

2008-01-24 Thread Ben Finney
Mike Kent <[EMAIL PROTECTED]> writes: > A bug issue has been opened in the Python Trac system for this. Wouldn't it be better to report it in the official Python bug tracker http://bugs.python.org/>, which is Roundup, not Trac? -- \ "The right to use [strong cryptography] is the right to

Re: Can someone explain this unexpected raw_input behavior?

2008-01-24 Thread Mike Kent
> If it weren't for the documentation... > > "If the prompt argument is present, it is written to *standard output* > without a trailing newline." > > -- > mvh Björn I have reported this issue to the python-dev mailing list, and Guido agrees that this is a bug in Python. It turns out that the ke

Re: Can someone explain this unexpected raw_input behavior?

2008-01-24 Thread BJörn Lindqvist
On Jan 24, 2008 8:08 AM, Gabriel Genellina <[EMAIL PROTECTED]> wrote: > En Thu, 24 Jan 2008 01:00:53 -0200, Mike Kent <[EMAIL PROTECTED]> escribió: > > > Gabriel, thank you for clarifying the source of this behavior. Still, > > I'm surprised it would be hard-coded into Python. Consider an > > int

Re: Can someone explain this unexpected raw_input behavior?

2008-01-23 Thread Gabriel Genellina
En Thu, 24 Jan 2008 01:00:53 -0200, Mike Kent <[EMAIL PROTECTED]> escribió: > Gabriel, thank you for clarifying the source of this behavior. Still, > I'm surprised it would be hard-coded into Python. Consider an > interactive program, that asks the user several questions, and > displays paragrap

Re: Can someone explain this unexpected raw_input behavior?

2008-01-23 Thread Ben Finney
Mike Kent <[EMAIL PROTECTED]> writes: > Consider an interactive program, that asks the user several > questions, and displays paragraphs of information based on those > questions. The paragraphs are output using print, and the questions > are asked via raw_input. Okay so far. > You want to do so

Re: Can someone explain this unexpected raw_input behavior?

2008-01-23 Thread Mike Kent
Gabriel, thank you for clarifying the source of this behavior. Still, I'm surprised it would be hard-coded into Python. Consider an interactive program, that asks the user several questions, and displays paragraphs of information based on those questions. The paragraphs are output using print, a

Re: Can someone explain this unexpected raw_input behavior?

2008-01-23 Thread Gabriel Genellina
En Wed, 23 Jan 2008 18:27:56 -0200, Mike Kent <[EMAIL PROTECTED]> escribió: > It's often useful for debugging to print something to stderr, and to > route the error output to a file using '2>filename' on the command > line. > > However, when I try that with a python script, all prompt output from

Can someone explain this unexpected raw_input behavior?

2008-01-23 Thread Mike Kent
It's often useful for debugging to print something to stderr, and to route the error output to a file using '2>filename' on the command line. However, when I try that with a python script, all prompt output from raw_input goes to stderr. Consider the following test program: === Start test.py ===