RetroSearch Browse

Mon Jun 12 22:05:52 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-June/065952.html

On Mon, Jun 12, 2006 at 03:12:20PM -0400, Phillip J. Eby wrote:
> encountered this myself.  I *have* seen some developers make spurious 
> "cleanups" to working code that breaks compatibility with older Python 
> versions, though, just not in wsgiref.

Note that the standard library policy has always been that the library
for Python 2.X does not need to work with an earlier Python
interpreter.  Modules that must continue to work with earlier
versions are listed in PEP 291.

(Yes, another PEP to look at in addition to 360.  IMHO we should
require all modules with version constraints or external master source
to have comments indicating this *in the code*, at the top of every
source file, so that someone writing a patch or bugfix knows what the
requirements are.)

--amk

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/065952.html below:

[Python-Dev] External Package Maintenance (was Re: Please stopchanging wsgiref on the trunk)