Fredrik Lundh writes:
>yes, I think it's bad. I've been using Python since 1.2,
>and no other change has had the same consequences
>(wrt. time/money required to fix it)
There are more things in 1.6 that might require fixing existing code:
str(2L) returning '2', the int/long changes, the Unicode changes, and
if it gets added, garbage collection -- and bugs caused by those
changes might not be catchable by a nanny. IMHO it's too early to
point at the .append() change as breaking too much existing code;
there may be changes that break a lot more. I'd wait and see what
happens once the 1.6 alphas become available; if c.l.p is filled with
shrieks and groans, GvR might decide to back the offending change out.
(Or he might not...)
--
A.M. Kuchling http://starship.python.net/crew/amk/
I have no skills with machines. I fear them, and because I cannot help
attributing human qualities to them, I suspect that they hate me and will kill
me if they can.
-- Robertson Davies, "Reading"
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4