Who uses input()? [was Re: question on "input"]
Nathan Pinno
falcon3166 at hotmail.com
Mon Jul 18 01:19:45 EDT 2005
I use input() all the time. I know many people say it ain't safe, but
whose going to use it to crash their own comp? Only an insane person would,
or a criminal trying to cover his/her tracks.
Sorry if I waded into the debate, but this debate originated from one of
my posts.
Nathan Pinno
----- Original Message -----
From: "Stephen Thorne" <stephen.thorne at gmail.com>
To: <hancock at anansispaceworks.com>
Cc: <python-list at python.org>
Sent: Sunday, July 17, 2005 11:12 PM
Subject: Re: Who uses input()? [was Re: question on "input"]
> On 15/07/05, Terry Hancock <hancock at anansispaceworks.com> wrote:
>> On Thursday 14 July 2005 07:00 am, Michael Hoffman wrote:
>> > Devan L wrote:
>> > > Use raw_input instead. It returns a string of whatever was typed.
Input
>> > > expects a valid python expression.
>> >
>> > Who actually uses this? It's equivalent to eval(raw_input(prompt))
but
>> > causes a lot of newbie confusion. Python-dev archives revealed that
>> > someone tried to get this deprecated but Guido disagreed.
>>
>> I don't think it should disappear, but it *does* seem more sensible for
>> "raw_input" to be called "input" (or "readstring" or some such thing)
and
>> "input" to vanish into greater obscurity as "eval_input" or something.
>>
>> Unfortunately, that would break code if anything relied on "input", so
I
>> guess that would be a Py3K idea, and maybe the whole I/O concept
>> will be rethought then (if the "print" statement is going to go away,
>> anyway).
>
> I don't see as "break input() using code" -> "not until py3k" as a
> logical cause/effect. No one should be using input() anyway, the only
> place it's at-all appropriate is in a python tutorial, with the 'guess
> the number' game.
>
> --
> Stephen Thorne
> Development Engineer
> --
> http://mail.python.org/mailman/listinfo/python-list
>
More information about the Python-list
mailing list