PEP 260: simplify xrange()

[Ralf Muschall]

Roman Suzi <rnd at onego.ru> writes:

> in webified forms (somewhere). If gcc people will want to remove, say,
> scanf function, they will certainly find that Linux kernel uses it ;-)

No, it doesn't (I just (find -exec grep)ped it (but I didn't expect such
a wart there anyway)).

Only a few standalone programs living there use it, and a SCSI driver
defines its own function "dc390_scanf" (which calls stroul) and is
found therefore.

Btw., am I the only one who thinks that removing scanf would be a good
idea (for the libc people, not the gcc ones)?  Do they accept CDPs[1]?

> Then GvR just googles around to find out that, OK, xrange is not used
> anywhere in the 3 month old code, so we should remove it from CVS.

CVS is such a powerful protocol that this could be happen
automatically, giving GvR more time to add continuations and monads.

Another problem is people who write text like
   "don't use xrange(a)[b:c]"
and put *that* on the web.  Since google's philosophy
is "be fast and complete, not smart", this will never be recognized.

[1] C depletion proposal

Ralf