This is a multi-part message in MIME format.
--------------93293161D9DE985912DCB2D9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Since the subject has come up several times recently,
and some one (Walter?) suggested a PEP be written....here goes.
Attached is a draft PEP. Comments?
Neal
--------------93293161D9DE985912DCB2D9
Content-Type: text/plain; charset=us-ascii;
name="pep-nn.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="pep-nn.txt"
PEP: XXX
Title: Backward Compatibility for Standard Library
Version: $Revision:$
Last-Modified: $Date:$
Author: neal@metaslash.com (Neal Norwitz)
Status: Draft
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
versions of Python.
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.
Backward Compatible Packages & Modules
Package/Module Maintainer(s) Python Version
-------------- ------------- --------------
distutils Andrew Kuchling 1.5.2
email Barry Warsaw 2.1
sre Fredrik Lundh 1.5.2
xml (PyXML) Martin v. Loewis 2.0
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:
--------------93293161D9DE985912DCB2D9--
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4