Guido van Rossum wrote:
> But they typically aren't used to entering EOF either; EOF is not
> exactly a typical input in an interactive program, and having to enter
> it typically means you're talking to a Unix utility that's not really
> designed for interactive use.
the progression I had in mind was
1. literals, simple operations, printing the result
2. reading input from the console, simple operations, printing
the result
3. reading input from a file, simple operations, printing the
result
the jump between 2 and 3 is a bit too large in today's Python.
another way to address that would be to add standard input and output
*objects* (which delegates to sys.stdin/stdout) to the builtin name-
space; after all:
input.readline()
is pretty self-documenting, even if you don't really understand dotted
notation just yet.
</F>
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
