#20874: update tutorial wording: sophisticated line editing is now standard.

Patch by Rafael Mejia.

diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index 8e8395a3496ddea0c70fae48c0586393a2573766..398ed72209b6b609999bafd4273df678b6157062 100644 (file)
--- a/Doc/tutorial/interpreter.rst
+++ b/Doc/tutorial/interpreter.rst
@@ -35,10 +35,9 @@ Windows) at the primary prompt causes the interpreter to exit with a zero exit
 status.  If that doesn't work, you can exit the interpreter by typing the
 following command: ``quit()``.
 
-The interpreter's line-editing features usually aren't very sophisticated.  On
-Unix, whoever installed the interpreter may have enabled support for the GNU
-readline library, which adds more elaborate interactive editing and history
-features. Perhaps the quickest check to see whether command line editing is
+The interpreter's line-editing features include interactive editing, history
+substitution and code completion on systems that support readline.
+Perhaps the quickest check to see whether command line editing is
 supported is typing Control-P to the first Python prompt you get.  If it beeps,
 you have command line editing; see Appendix :ref:`tut-interacting` for an
 introduction to the keys.  If nothing appears to happen, or if ``^P`` is echoed,