will python 3000 break my code?
gerrit at nl.linux.org
Wed Mar 1 10:17:11 CET 2000
<quote name="Fredrik Lundh" date="951897778" email="effbot at telia.com">
> Gerrit Holl <gerrit at nl.linux.org> wrote:
> > 1) l.append changes in Python 1.6, not in P3K,
> > 2) it's such a small change; it will be able to be done automatically,
> nope. the only way to fix this automatically is to patch the
> python interpreter to support the old behaviour.
I think the Python interpreter can be patched to give warnings, like
it does when exceptions are raised in __del__ or when you use the
> "checkappend" can only spot obvious cases. to make sure your
> program works fine, careful regression testing is the only thing
> that will help.
> > 3) it's considered Bad Style to use multi-argument append, IMHO.
> ahem. does your HO really matter to all those who have
> to spend time and money changing their existing code base.
No, it doesn't. But IIRC, it's nowhere documented and it only
works because of the current implementation.
> preliminary results indicate that *all* our applications and
> libraries (including PIL) are affected by this change. given
> that, it's quite likely that a few other companies will also
> stumble upon this one...
I *think* it's also Guido's HO, otherwise I don't understand why
he changed the implementation.
-----BEGIN GEEK CODE BLOCK----- http://www.geekcode.com
GCS dpu s-:-- a14 C++++>$ UL++ P--- L+++ E--- W++ N o? K? w--- !O !M !V PS+ PE?
Y? PGP-- t- 5? X? R- tv- b+(++) DI D+ G++ !e !r !y
-----END GEEK CODE BLOCK-----
More information about the Python-list