From fcf3a0c55bc38943647d9145e214ca3b6f8b5577 Mon Sep 17 00:00:00 2001
From: Georg Brandl <georg@python.org>
Date: Tue, 28 Dec 2010 09:18:24 +0000
Subject: Remove confusing paragraph -- this is relevant only to advanced users
 anyway and does not belong into the tutorial.

---
 Doc/tutorial/interpreter.rst | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index 20fae9a..8d743de 100644
--- a/Doc/tutorial/interpreter.rst
+++ b/Doc/tutorial/interpreter.rst
@@ -58,14 +58,6 @@ Some Python modules are also useful as scripts.  These can be invoked using
 ``python -m module [arg] ...``, which executes the source file for *module* as
 if you had spelled out its full name on the command line.
 
-Note that there is a difference between ``python file`` and ``python
-<file``.  In the latter case, input requests from the program, such as calling
-``sys.stdin.read()``, are satisfied from *file*.  Since this file has already
-been read until the end by the parser before the program starts executing, the
-program will encounter end-of-file immediately.  In the former case (which is
-usually what you want) they are satisfied from whatever file or device is
-connected to standard input of the Python interpreter.
-
 When a script file is used, it is sometimes useful to be able to run the script
 and enter interactive mode afterwards.  This can be done by passing :option:`-i`
 before the script.  (This does not work if the script is read from standard
-- 
cgit v0.12