Anand Balachandran Pillai schrieb: > Still this seems like a bad thing to break backward compatibility with. > However I cannot really provide a use-case apart from what Benjamin > has said -> Teaching. It is not a common use-case to equate ranges > in code and that is bad coding anyway. > > Hopefully, this will be well documented at 3.0 release. Currently > that "whats new" page does not mention anything about the range > type and how it breaks backward compatibility.
It says "xrange() renamed to range()". While this is everything one'd need to know, I agree that it could use a clarifying sentence, so I added one now. Georg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
