2002-06-06 15:25:31 -04:00
|
|
|
|
PEP: 291
|
|
|
|
|
Title: Backward Compatibility for Standard Library
|
|
|
|
|
Version: $Revision$
|
|
|
|
|
Last-Modified: $Date$
|
|
|
|
|
Author: neal@metaslash.com (Neal Norwitz)
|
|
|
|
|
Status: Active
|
|
|
|
|
Type: Informational
|
|
|
|
|
Created: 06-Jun-2002
|
|
|
|
|
Post-History:
|
|
|
|
|
Python-Version: 2.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Abstract
|
|
|
|
|
|
|
|
|
|
This PEP describes the packages and modules in the standard
|
|
|
|
|
library which should remain backward compatible with previous
|
2003-12-04 10:12:55 -05:00
|
|
|
|
versions of Python. If a package is not listed here, then it need
|
|
|
|
|
only remain compatible with the version of Python it is
|
|
|
|
|
distributed with.
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Rationale
|
|
|
|
|
|
|
|
|
|
Authors have various reasons why packages and modules should
|
|
|
|
|
continue to work with previous versions of Python. In order to
|
|
|
|
|
maintain backward compatibility for these modules while moving the
|
|
|
|
|
rest of the standard library forward, it is necessary to know
|
|
|
|
|
which modules can be modified and which should use old and
|
|
|
|
|
possibly deprecated features.
|
|
|
|
|
|
|
|
|
|
Generally, authors should attempt to keep changes backward
|
|
|
|
|
compatible with the previous released version of Python in order
|
|
|
|
|
to make bug fixes easier to backport.
|
|
|
|
|
|
2002-11-15 17:53:27 -05:00
|
|
|
|
In addition to a package or module being listed in this PEP,
|
|
|
|
|
authors must add a comment at the top of each file documenting
|
|
|
|
|
the compatibility requirement.
|
|
|
|
|
|
2003-12-04 10:12:55 -05:00
|
|
|
|
When a major version of Python is released, a CVS branch is
|
|
|
|
|
created for continued maintenance and bug fix releases. A package
|
|
|
|
|
version on a branch may have a different compatibility requirement
|
|
|
|
|
than the same package on the trunk (i.e. current bleeding-edge
|
|
|
|
|
development). Where appropriate, these branch compatibilities are
|
|
|
|
|
listed below.
|
|
|
|
|
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
Features to Avoid
|
|
|
|
|
|
|
|
|
|
The following list contains common features to avoid in order
|
|
|
|
|
to maintain backward compatibility with each version of Python.
|
|
|
|
|
This list is not complete! It is only meant as a general guide.
|
|
|
|
|
|
2002-11-29 20:50:39 -05:00
|
|
|
|
Note that the features below were implemented in the version
|
|
|
|
|
following the one listed. For example, features listed next to
|
|
|
|
|
1.5.2 were implemented in 2.0.
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
2002-11-29 20:50:39 -05:00
|
|
|
|
Version Features to Avoid
|
|
|
|
|
------- -----------------
|
2002-06-06 15:25:31 -04:00
|
|
|
|
1.5.2 string methods, Unicode, list comprehensions,
|
|
|
|
|
augmented assignment (eg, +=), zip(), import x as y,
|
|
|
|
|
dict.setdefault(), print >> f, calling f(*args, **kw),
|
2002-11-29 20:50:39 -05:00
|
|
|
|
plus all features below
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
2.0 nested scopes, rich comparisons, function attributes,
|
2002-11-29 20:50:39 -05:00
|
|
|
|
plus all features below
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
2.1 use of object or new-style classes, iterators,
|
|
|
|
|
using generators, nested scopes, or //
|
|
|
|
|
without from __future__ import ... statement,
|
2002-11-29 20:50:39 -05:00
|
|
|
|
plus all features below
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
2.2 bool, True, False, basestring, enumerate(), {}.pop(),
|
2002-11-29 20:50:39 -05:00
|
|
|
|
PendingDeprecationWarning, Universal Newlines
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Backward Compatible Packages, Modules, and Tools
|
|
|
|
|
|
2003-12-04 10:12:55 -05:00
|
|
|
|
Package/Module Maintainer(s) Python Version Notes
|
|
|
|
|
-------------- ------------- -------------- -----
|
2003-12-04 10:16:00 -05:00
|
|
|
|
bsddb Greg Smith 2.1
|
|
|
|
|
Barry Warsaw
|
2002-06-06 15:25:31 -04:00
|
|
|
|
compiler Jeremy Hylton 2.1
|
2004-08-19 18:58:30 -04:00
|
|
|
|
decimal Raymond Hettinger 2.3 [2]
|
2004-11-10 03:22:51 -05:00
|
|
|
|
distutils Andrew Kuchling 2.1
|
2003-12-04 10:12:55 -05:00
|
|
|
|
email Barry Warsaw 2.1 / 2.3 [1]
|
2002-11-15 17:53:27 -05:00
|
|
|
|
logging Vinay Sajip 1.5.2
|
2003-07-02 17:07:42 -04:00
|
|
|
|
sre Fredrik Lundh 2.1
|
2004-10-13 11:57:42 -04:00
|
|
|
|
subprocess Peter Astrand 2.2
|
2002-06-06 15:25:31 -04:00
|
|
|
|
xml (PyXML) Martin v. Loewis 2.0
|
2004-08-20 03:32:06 -04:00
|
|
|
|
xmlrpclib Fredrik Lundh 2.1
|
2003-12-04 10:16:00 -05:00
|
|
|
|
modulefinder Thomas Heller 2.2
|
|
|
|
|
Just van Rossum
|
2004-05-05 20:29:47 -04:00
|
|
|
|
platform Marc-Andre Lemburg 1.5.2
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Tool Maintainer(s) Python Version
|
|
|
|
|
---- ------------- --------------
|
2002-11-15 17:53:27 -05:00
|
|
|
|
None
|
2002-06-06 15:25:31 -04:00
|
|
|
|
|
|
|
|
|
|
2003-12-04 10:12:55 -05:00
|
|
|
|
Notes
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
|
|
[1] The email package version 2 was distributed with Python up to
|
|
|
|
|
Python 2.3, and this must remain Python 2.1 compatible. email
|
|
|
|
|
package version 3 will be distributed with Python 2.4 and will
|
|
|
|
|
need to remain compatible only with Python 2.3.
|
|
|
|
|
|
2004-08-19 18:58:30 -04:00
|
|
|
|
[2] Specification updates will be treated as bugfixes and backported.
|
|
|
|
|
Python 2.3 compatibility will be kept for at least Python 2.4.
|
|
|
|
|
The decision will be revisited for Python 2.5 and not changed
|
|
|
|
|
unless compelling advantages arise.
|
|
|
|
|
|
2003-12-04 10:12:55 -05:00
|
|
|
|
|
2002-06-06 15:25:31 -04:00
|
|
|
|
Copyright
|
|
|
|
|
|
|
|
|
|
This document has been placed in the public domain.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local Variables:
|
|
|
|
|
mode: indented-text
|
|
|
|
|
indent-tabs-mode: nil
|
|
|
|
|
sentence-end-double-space: t
|
|
|
|
|
fill-column: 70
|
|
|
|
|
End:
|