How to break? (was Re: A modest PEP0238 suggestion)

[Aahz Maruch]

In article <bZC87.37029$EP6.9803880 at news1.rdc2.pa.home.com>,
Terry Reedy <tjreedy at home.com> wrote:
>
>One way to never break code, silently or otherwise, is to never change
>the interpreter.
>
>Another is to make current behaviour (including bugs) the default
>forever and forever require explicit import of every change ever made
>since freeze time, with runtime compilations handled separately.
>
>Another is to go ahead and make new meanings the default but forever
>identify every construct that once had a different meaning and issue a
>warning so that the change is never completely silent.
>
>Any others?

Yup: make the old behavior an error but also require a directive to
enable the new behavior.
-- 
                      --- Aahz  <*>  (Copyright 2001 by aahz at pobox.com)

Hugs and backrubs -- I break Rule 6                 http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista   

Fortune cookie: Watch your relations with other people carefully, be reserved.