Clarify the what the xrange representation issue was.
This commit is contained in:
parent
67465ada98
commit
55a199a5d1
|
@ -157,7 +157,12 @@ Accepted and completed
|
||||||
[at least I *think* it's done, as of 15-Aug-2000 - tim]
|
[at least I *think* it's done, as of 15-Aug-2000 - tim]
|
||||||
|
|
||||||
* Fix xrange printing behavior - Fred Drake
|
* 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
|
Accepted and in progress
|
||||||
|
|
Loading…
Reference in New Issue