Clarify the what the xrange representation issue was.

pep-0200.txt

@@ -157,7 +157,12 @@ Accepted and completed
       [at least I *think* it's done, as of 15-Aug-2000 - tim]
 
     * Fix xrange printing behavior - Fred Drake
-      [although I'm not sure what this one was talking about - tim]
+      Remove the tp_print handler for the xrange type; it produced a
+      list display instead of 'xrange(...)'.  The new code produces a
+      minimal call to xrange(), enclosed in (... * N) when N != 1.
+      This makes the repr() more human readable while making it do
+      what reprs are advertised as doing.  It also makes the xrange
+      objects obvious when working in the interactive interpreter.
 
 
 Accepted and in progress