[Python-Dev] deprecating string module?

Barry A. Warsaw barry@zope.com
Wed, 29 May 2002 09:11:02 -0400

>>>>> "MAL" == M  <mal@lemburg.com> writes:

    MAL> Just look at the hoops which the email package has to go
    MAL> through to maintain such compatibility.

That's not a great analogy though.  email's got those compatibility
modules largely because generators were such a natural fit for three
of the methods.  I wrote them in Py2.2 first to learn how to use
generators and then had to figure out how to backport them.

email only works with Python 2.1 and beyond, with a strong bias
against the string module.

All in all, I'm still not convinced that the compatibility modules are
worth it, but for now, I'm sticking with them.  They definitely cause
pain with distutils. ;/

There's a price to be paid for living on the bleeding edge (or scabbed
edge for Python 2.2 ;).  But there's also a price to pay for
maintaining backwards compatibility and sticking with that forever,
More important (to me) than the feature or perceived stability of
Py1.5.2, is that so much has been fixed by Python 2.1.3 that it made
no sense to use anything earlier.  I think/hope that the PBF's Pytie
releases will help ease that pain.