Why should input(prompt="h ello:") fail?

[zhi]

Really confused, when I use keyword style argument as following:

input(prompt="h ello")

Traceback (most recent call last):
File "<pyshell#5 2>", line 1, in -toplevel-
input(prompt="h ello")
TypeError: input() takes no keyword arguments

While the library reference says the function is: input( [prompt])
so, it should work.:(

I am using python 2.3 for windows.
Have anyone tried this?
I am new to python, please help me, thanks.

[Skip Montanaro]

Note however that input() is a poor choice for serious work: you
should quickly get past the point of wanting to use it and learn why
raw_input() is a better choice.

Michele> Very true. Is "input" a candidate for deprecation in 3.0? If
Michele> not, here I give my vote to put "input" in the black list ;)

Even better, deprecate input() and rename raw_input() to input()...

Skip

[Peter Hansen]

Skip Montanaro wrote:

>> Note however that input() is a poor choice for serious work: you
>> should quickly get past the point of wanting to use it and learn why
>> raw_input() is a better choice.

Michele> Very true. Is "input" a candidate for deprecation in 3.0? If
Michele> not, here I give my vote to put "input" in the black list ;)

Even better, deprecate input() and rename raw_input() to input()...

If you mean do those two things at the same time, you've just deprecated the
use of "input" and then provided only a routine named "input"...

And if you mean to separate them with one release to give time for the
deprecation notice to spread around, you'll just confuse people when you
then add "input" back in, but with different functionality.

(I agree with the idea of reusing the name input() for the One True Input
Routine, but not with deprecating anything as it will just confuse the issue.)

-Peter

[Aahz]

In article <3F************ ***@engcorp.com >,
Peter Hansen <pe***@engcorp. com> wrote:

Skip Montanaro wrote:

Even better, deprecate input() and rename raw_input() to input()...

If you mean do those two things at the same time, you've just
deprecated the use of "input" and then provided only a routine named
"input"...

And if you mean to separate them with one release to give time for the
deprecation notice to spread around, you'll just confuse people when
you then add "input" back in, but with different functionality.

(I agree with the idea of reusing the name input() for the One True
Input Routine, but not with deprecating anything as it will just
confuse the issue.)

Yeah, what would make more sense would be to rename input() to
eval_input() and rename raw_input() to input(), and immediately
deprecate eval_input().
--
Aahz (aa**@pythoncra ft.com) <*> http://www.pythoncraft.com/

Weinberg's Second Law: If builders built buildings the way programmers wrote
programs, then the first woodpecker that came along would destroy civilization.