Warning switches (was: Python 1.6 alpha 1 released)

Fredrik Lundh effbot at telia.com
Tue Apr 4 17:33:07 EDT 2000

Johannes Stezenbach <yawyi at gmx.de> wrote:
> >However, I'll do so for purely backwards compatible reasons, and I
> >will continue to press for the tuple address as the correct form.
> Will python then support a -w switch to support people in writing
> correct programs (i.e. compatible with likely furure language/library
> changes), just like our-favourite-four-letter-P-language?

how about -v<version> ?

there has been talks about compatibility "modes" (probably an option,
but probably also a way to set options programmatically), as a way to
help people prepare for "Python 3000".  I think we might expect some
of it in 1.7, and more of it in 1.8 (if that ever materializes).

but hopefully, Python 3000 will be completely free from modes.

> Seriously: Either accept the 2-arg form of connect() as *correct* for
> all future versions of python or keep the change to make it illegal
> *now*.

guido tried to do the latter.  guess he didn't expect that everyone was
using connect in every single script they'd written ;-)

> Just postponing the change is evil since it will only hurt more people
> in the future, as the number of python users is growing. (CP4E?)

yeah, but at the moment, guido and the rest of the 1.6 team have
more important things to do than to deal with the spanish inquisition.
so I'm afraid it'll have to wait until that -v1.6 switch is in place.

> If it's not broken then don't fix it.

    "I try to avoid breaking user programs, but if something
    needs to be done it really needs to be done."
    -- linus torvalds


More information about the Python-list mailing list